Steven Zahm@ Craig
RE: Is a search possible on an added text box or checkboxes?
On custom text boxes yes, as long as it is registered as covered in the dev docs here:
https://connections-pro.com/quicktip-custom-field-adding-a-text-field/
Navigate to the Connections : Settings admin page and click the Search tab and enable search for your text field.
RE: I am confused by the words “Custom Fields” in the screen shot attached. Why does that show and how do I remove?
Yep, I understand. The confusion itself comes directly from WP. I’ll try to explain…
Pre WP5 if you scrolled to the bottom of the edit page/post admin page you would find a section named “Custom Fields”. This was a generic way to add support in core WP. In WP5, you need a plugin to enable this feature again.
https://wordpress.org/plugins/custom-fields-gutenberg/
Now, on the add/edit page/post admin page you would find other sections, called metaboxes, often added by themes and plugins. These are called “custom fields”. Notice the lack of capitalization.
Connections mimics this feature. So it has a “Custom Fields” section (metabox) and “custom fields” can be registered as covered in the dev docs.
So, the way to turn the “Custom Fields” on the template … navigate to the Connections : Settings admin page and click the Display tab. Scroll to the Result List Content Block section and disable the “Custom Fields” option. Now scroll down further to the Entry Content Block section and disable the “Custom Fields” option. Save the changes.
RE: You don’t show how to add the checkboxes to imports and exports. Is it the same as the text field? Can I use the same code,
Yes, these can be imported and you can, mostly, use the same code. Take a look in the DB in the entry meta table. Find one of you custom fields for checkboxes. You’ll find it as JSON encoded data. Depending how you want it imported from CSV determines how you need to alter the code to import the field. If your JSON encode your data, it should just work.
This is very hard to document because it depends entirely on the source data and the options key/value pairs when registering the field. Same goes for CSV Export, but basically in reverse.
Hope this helps.