|
awalzer
|
December 8, 2016 at 9:31 am
After upgrading from a previous version of ACF Pro to the latest (5.5.1) we can no longer add field groups to some custom post types, notably Event Espresso (espresso_events) and My Calendar (mc_events). Both of them showed up prior to the update, but now it just shows a single Event post type that doesn’t seem to be connected to either.
I looked at a copy of our site prior to updating ACF and it works fine. I contacted the ACF developers and they investigated a little and their explanation was that it was because the events aren’t saved as custom post types but as pages.
I don’t know why this would explain why it was working prior to updating ACF though.
Any ideas?
|
|
Tony
|
December 8, 2016 at 9:40 am
Hi there,
Are you using EE3 or EE4?
Did you update/change themes at the same time as updating?
If you de-activate My Calendar and try with just EE and ACF pro, does the espresso_events post type show then?
|
|
awalzer
|
December 8, 2016 at 12:03 pm
We are using EE4 and only updated the ACF plugin. When we deactivate the My Calendar plugin, there is totally no mention of any Event within ACF when trying to choose a post type.
|
|
Josh
|
December 8, 2016 at 12:34 pm
What they said about Event Espresso isn’t correct. Events are custom post types, they are not pages.
You though, are correct. They should probably investigate why it was working prior to updating ACF.
|
|
awalzer
|
December 8, 2016 at 12:58 pm
This was their reasoning:
It seems that the plugins in questions do not store their posts as custom post types. They are saved as pages.
http://www.camarilloyoga.com/wp-admin/admin.php?page=espresso_events
In order for this to be loaded as a post type the url should be such as
http://www.camarilloyoga.com/wp-admin/admin.php?post_type=espresso_events
I’ll let them know what you said though and hopefully they can figure out what’s changed since the update.
|
|
Josh
|
December 8, 2016 at 1:04 pm
That’s also incorrect, and possibly there’s code in the new version of ACF Pro that follows that incorrect assumption. Custom post types can load on other admin routes.
|
