Home›Types Community Support›[Closed] Notice: map_meta_cap was called incorrectly. The post type service is not regist
[Closed] Notice: map_meta_cap was called incorrectly. The post type service is not regist
The Toolset Community Forum is closed, for technical support questions, please head on to our Toolset Professional Support (for paid clients), with any pre-sale or admin question please contact us here.
This is the community support forum for Types plugin, which is part of Toolset. Toolset is a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients and people who registered for Types community support can post in it.
When I try to edit custom post type "service" or ant another custom post type with "Visual Composer" at frontend editor - I have that notice hidden link . Test it, please, by yourself and tell my thr soluyion of that problem.
Thank you for contacting Toolset support. I am not able to reproduce this issue at my end with updated version of Toolset plugins and Visual composer Version 5.2.
3. Could you please also try to check it by deactivating all third-party plugins (except Toolset and Beaver Builder) and switching back to the Default Theme (e.g. Twenty Sixteen theme) to see for any possible conflicts with any of the plugins or themes?
Hello!
Sorry for long answer
1) I use last version of your plugin.
2) I added debug info after turned on Default Theme (Twenty Seventeen theme) and turned off all third-party plugins (except Toolset and Visual Composer) and still have same notice hidden link
This issue is forwarded to our development team. In the meantime I would suggest you to please disable WP Debug mode in your wp-config.php file.
And use Backend Editor of Visual Composer to edit posts (if frontend editor is not allowing you to edit post). This notice only appears when we enable WP Debug mode.
I see in our internal system that Visual composer needs to change some of their code, its post type and registration priority issue. The change most likely won't happen in our plugin but in VC and we usually inform them in such cases. I have followed up with our development team and I will update you according.
Just wanted to share the update, that our development team has passed the info needed in this case to the Visual Composer team, so they can analyze the CPT registration priority issue and provide a fix accordingly. As soon as I hear more, I will update you.
