Steven Zahm@ Brian
RE: I thought this was supposed to be resolved with the latest update? Is there something I am missing?
The search has been expanded to support registered text and textarea custom fields registered following this tutorial.
I took a look at your site, nice work on customizing cMap! It appears you are using the “Custom Fields” metabox in the admin vs using the custom fields covered in the tutorial. This might be a bit confusing.
Apologies for the confusion! It stems from core WordPress terminology. The “Custom Fields” metabox (with the drop down) are different from the registered “custom fields”. I’ll try to explain…
Take a look at the add WordPress Page/Post, you will also find the “Custom Fields” metabox… and, very likely, you’ll have “custom fields” added by the theme and other plugins. The “custom field” added by following the tutorial adds new custom fields like the theme and plugins added fields to the add page/post.
So…
The custom field added by following the tutorial will display as its own metabox as its own input just as they do when the theme or plugin adds a “custom field” to the WordPress page/post page. It is these that search was expanded to support.
What can you do…
You can still follow the tutorial and use your existing data. When registering the text fields, for the field_id use the Name, exactly, as entered in the “Custom Fields” metabox. Do this will cause the the field to become private and will no longer be listed in the “Custom Fields” metabox. Instead it will show up as a new input field with you existing data.
You will also need to update the template following the tutorial so the data will be displayed.
And search… after you do the above, if you navigate to the Connections : Settings admin page and click the Search tab, you’ll find you have the option to define which fields will be searched. You can enable the custom fields you wish to have searched.
I hope this makes sense, let me know.