Posted: October 30, 2015 at 3:42 pm
|
Have _events and _venues post types lost their support capabilities for Advanced custom fields since the second most recent update? It’s vital I have them as ACF adds much needed additional info for my events and venues. For example, I use ACF to add finer geo-mapping http://www.trailadventures.uk/events/womens-mountain-biking-lesson-november/. Please get back ASAP as I have a number of new event to put live. Thanks |
Hi Phil, I’m not sure that I understand what is broken as the Google map that is on your events page is not from Event Espresso: http://cl.ly/image/1N2r0H1c3r2s Could you provide more information? Thanks — |
|
|
Hi Lorenzo, Thanks for the quick response. That’s right the map on my events pages are generated by the Advanced Custom Fields (ACF) plugin. I have been using the plugin as it allows me pin-point accuracy when adding map markers (required as I work outdoors). My example show’d a map that I generated prior EE4 update. I was able to add the ACF meta box to espresso_events and espresso_venues post types using the standard rules that ACF provides – all was working well. Since the EE4 update the fields are no longer displaying within the post editor for either of the EE4 post types. I have tested standard pages and post and other custom post types and the field are all showing currently. Thoughts please? Phil |
Hi Phil, As far as I can tell, nothing has changed in EE with the event editor where it would no longer allow ACF to add metaboxes, and I have site that used ACF with EE and it continues to work there. It may help to know which version of ACF you have, and if there are other plugins active that affect the admin editor screens. One other thing you can try, just to see if it’s the update or something else, is you download the prior version of Event Espresso that you updated from to see if it works again with that version. You can download prior releases of Event Espresso from the github repo here: https://github.com/eventespresso/event-espresso-core/releases |
|
|
Josh, Lorenzo Problem solved! Simply a meta naming issue (odd that it worked previously). The ACF meta field name and key were Event location and event-location respectively and conflicted with meta used by EE. I renamed my ACF fields and hey presto, my extra custom fields appeared. Thanks for the responses and good to get this sorted. Cheers Phil |
Hi Phil, I’m glad to hear you got this sorted. |
|
The support post ‘Advanced custom fields no longer display since update’ 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.