Firstly, thanks for creating this plugin. Having migrated from using the Sniplets plugin, it’s great and does a very great job of helping to create re-usable content, quickly and easily. Good work on building a very powerful plugin!
There is, however, an issue I’m experiencing and wonder if you (or anyone else) can help with? It’s to do with the Shortcodes UI plugin using the “Custom Post Types” functionality to create the shortcodes, which is now causing an issue with another plugin I’m using.
The shortcodes created are being identified as “Posts/Pages” and the output also contains filtered content from other plugins.
The plugin I’m using is WP eMember. This plugin has a “Bookmark” feature that identifies Posts/Pages and then adds an icon so a user can bookmark the page.
The problem is, it is also (correctly) identifying *all* of the shortcodes positions created with Shortcodes UI plugin (since these shortcodes are Custom Posts)! As a consequence, at each point in a page where a Shortcodes UI shortcode is placed, there is also a bookmark icon added.
This issue may be caused by the Shortcodes UI plugin using “Custom Post Types”. The content created by the Shortcodes UI plugin is being recognised by this (and maybe other) plugin(s) to be a type of custom Post or Page. When this happens, any filters for Post/Page types get applied as well.
Question: Is it possible to exclude this plugin from affecting other plugins that actually do need to use Custom Post Types? (i.e. using the data without any filters applied to the shortcode content).
I think it’s great that you’ve managed to leverage the Custom Post Type functionality to create a very cool plugin. It’s a very clever solution to the problem… However, I’m just wondering if “technically” the plugin is using the Custom Post Type functionality in the right way?
By this, I mean that it doesn’t create full custom Posts/Pages (as it only uses this feature to store the information easily). The plugin simply makes use of the building blocks provided, but this does seem to be having some very strange side effects… I guess it’s a “Custom Type” but maybe not a “Custom Post Type”.
What’s the best way of making sure that the plugin isn’t grabbing additional filtered content for Post Types? Any suggestions about how best to exclude this “Post Type” would be very welcome (or grabbing the data *before* any filters are applied, would be cool too!).
Thanks in advance!
- The topic ‘Custom Post Type Exclude Issue’ is closed to new replies.