Post smth pls to let me know that you read it and may be (or are going to) try to solve the problem.
The WordPress architecture is very difficult to work with: there are often plugins that conflict. I can take a look at this — I’m trying to release version 0.9.4 of my plugin.
The first thing I would try is to turn off any custom permalink structures for your custom content types: turn off the permalink structure entirely so your URLs look like this:
http://site.com/?post_type=book&p=39
I really hate how WP handles permalinks — it’s a poor implementation in my opinion, and there are all kinds of problems that arise trying to work around it, so that’s my first guess as to the problem.
I’m posting this in the bug tracker because it’s really more of a bug than a discussion. I’m working on other features/bugs now for a paying gig.
Looking at this, the WordPress SEO plugin has unhandled PHP notices… that’s a bad sign… so part of the problem here is with the other plugin — I can’t fix problems with other plugins, I can only make sure my plugin is running “correctly”.
Here’s the bug report I filed:
http://code.google.com/p/wordpress-custom-content-type-manager/issues/detail?id=189
Aha. There is an easy fix:
Go to the wp-content/plugins/custom-content-type-manager/loader.php file and edit the following line:
add_action('init', 'CCTM::register_custom_post_types', 1);
Change it so that the priority number is greater than 10, e.g.
add_action('init', 'CCTM::register_custom_post_types', 11 );
That fixes the problem.
I found
add_action('init', 'CCTM::register_custom_post_types', 0 );
and changed it to
add_action('init', 'CCTM::register_custom_post_types', 11 );
and… IT WORKS !!! GREAT ! Thank You very much 🙂
I will copy the fix to the “WordPress SEO”‘s bug report page to help people.
P.S.- your plugin is the door to custom types. I have created even the data base of the items. It is private but it works great. Although, custom/user taxonomy will be super feature/thing in your plugin. It is the best and it will be the best with this addition for long time…it may even become a classic/must_have_plugin.
So, thx one more time.
Eugene. http://1245.ru
Glad it works!
If you need custom taxonomies, try using momo360modena’s Simple Taxonomy:
http://ww.wp.xz.cn/extend/plugins/simple-taxonomy/
It is a well-constructed plugin and it integrates very well with CCTM.
I deactivated Custom Content Type manager and had to re-save the XML Sitemaps button for it to work.
I activated More Fields (http://ww.wp.xz.cn/extend/plugins/more-fields/) instead and the XML Sitemaps works properly.
Yeah. Thank you for finding this conflict!
Glad the solution works! It’ll be integrated into 0.9.4, which should be out in the next day or two.
hello,
i am having plugin conflict, when i activate simple taxonomy plugin, then CCTM plugin shows page not found error,when i deactivate it CCTM works fine, i checked for add_action(‘init’, ‘CCTM::register_custom_post_types’, 11 ); in loader.php, but the value was already 11, so i guess it is already updated,
i even added define( ‘SCOPER_DISABLE_MENU_TWEAK’, true )in wp-config.php, still it does not work and in CCTM.php i searched for add_menu_page() , but it is not there, please help me
Ugh. WordPress makes the life difficult for developers.
1. Where are you seeing a “page not found error”? Are you trying to view a post, or a page, or what???
2. What are your permalink settings? Have you checked that these all work?
3. I didn’t think the SCOPER_DISABLE_MENU_TWEAK was in the Simple Taxonomy plugin… I don’t think that has anything to do with the 404 problem you described. That’s related to an issue where the menu items don’t appear in the manager — are you experiencing that? The CCTM’s menu stuff is generated by a customizable config file: config/menu/admin_menu.php (but again, I don’t think that’s relevant).
Try looking through the loader.php — my guess is that one of the events is getting hijacked or isn’t handling an edge case. E.g. try commenting out this in loader.php:
add_filter('request', 'CCTM::request_filter');
And see if that changes anything.
Please always post the version of the plugin that you’re using, otherwise it’s very difficult to know where you’re coming from.
thanx for the reply!! 🙂
1. using CCTM plugin i created content type ‘portfolio’, the portfolio pages are listing, but when i click on any portfolio to go to details,it shows 404 error, but when i deactivate simple taxonomy plugin it works fine.
2. this error occurred while upgrading wordpress version to 3.4.2 and the version of plugin is 0.9.6
3. the permalink settings is set to post name
i tried commenting the add_filter(‘request’, ‘CCTM::request_filter’);
but it did not help
Are you really using 0.9.6? Or 0.9.6.1 (the most recent)?
If the problem comes up when you activate the Simple Taxonomy plugin, my guess is that the problem is in that plugin, but I have sympathy here since WP’s architecture here is very difficult to wrestle with: the way you have to customize requests to handle categories etc. is really low-tech and clumsy. The event-driven model explodes when there are too many plugins attached to the same events, and I suspect that’s what’s happening here.
It’s probably worth filing a bug report in the issue tracker: http://code.google.com/p/wordpress-custom-content-type-manager/issues/list
I like the Simple Taxonomy plugin, so I’d like to stay compatible with it — chances are good that when I implement taxonomy support, all the troubles here will be on my plate anyhow.
