Posted: June 24, 2021 at 9:45 am
We are still currently using Event Espresso 3, and have two questions:
1. We want to add a custom field to our “Add New Event” template to use on each of our future events created. The purpose of this is to add a formal event title for the course as we have to keep the regular Event Title very short for Google Event Mark Up.
I was trying to find answers online, and I saw it was previously recommended to use this Plugin, but I don’t understand how to use this within Event Espresso itself: https://wordpress.org/plugins/advanced-custom-fields/
What is the best option for what I’m trying to accomplish?
2. Is there another custom field we can add that includes check boxes? This really goes off of the first question, if this capability is available we would want another custom field.
Thank you so much!
Also, I forgot to include that I would need to include these fields in the Event Espresso export as well. Is this possible?
We found this feature, but we can’t find it on the backend.
Also, if so, would these be exportable fields?
Standard EE3 events are not custom post types so don’t support Custom Fields (and therefore the Advanced Custom Fields plugin) out of the box.
There is a way to set up Event Espresso to also create custom posts for your events (which will then allow the custom post type to work with ACF), however, that also means you work outside of the usual Event Espresso setup (the feature was added to allow advanced users/developers to pretty much roll their own).
EE3 events do have their own custom fields (event meta) which can be used for some values: https://monosnap.com/file/ozuQNVV6Y869MzJLzj5rpsPKnZCUZM
Those can then be accessed through functions within EE3 as event_meta but it depends on what you need to do if that will be useful, you can’t create checkbox fields for that without custom development.
Using the Event Meta values mentioned above it is possible, but not something we have a plugin for and I’m not aware of any that will work with Event Espresso out of the box.
For the amount of development time/work you would need for this you would be better switching to EE4. I know from your previous thread that the frontend output of the event doesn’t fit with your workflow, however, ACF is compatible with EE4 events out of the box (and including them in the export is much easier), meaning you could then focus your development time on getting the front end working how you prefer.
Thank you so much for your reply, Tony!
I’m going to try to do more testing with EE4 and see if we can figure out a way to make it work.
The support post ‘Custom Fields in Event Espresso 3’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.