Posted: May 6, 2014 at 10:35 am
|
hi can you tell me where to remove EE cpt like described in paragraph below. The process goes like this: Remove the PHP that declared these custom types. Normally, you’ll remove them from functions.php in the theme. Once you do this, all your custom data will appear to have vanished. Don’t worry. It just doesn’t show. |
Hi Gabriel, Event Espresso uses custom post types differently than themes. If you follow the above guide and remove the code where it registers the espresso_events, contacts, and espresso_venues Custom Post types it will do more than hide the custom data, it will break core functionality. With that, we don’t recommend trying to remove the core Event Espresso custom post types. If you want to see for yourself the many ways how removing the CPTs will break things, the file that Event Espresso uses to register its custom post types is /core/CPTs/EE_Register_CPTs.core.php. Please only try this on a testing setup, not a live site. |
|
|
so if i want to use Views, what do you suggest i do? I’d like to use EE4 a few client sites but each require a bit of customization and Views would really help me out, any ideas? -g |
|
how about Pods or ACF (advan. custom fields)? |
We’ve tested and recommend using Advanced Custom Fields. ACF works out of the box with Event Espresso without making any modifications to the Event Espresso code. |
|
|
ok but it works well with EE 4, correct? will try and let you know. thanks |
Event Espresso 4 works perfectly well with Advanced Custom Fields. |
|
The support post ‘EE 4 integration with Views by wp-toolset’ 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.