123 pointsSerious WPMU DEV-sterI'm new here
jzvestor
Member
—
7th February 2012
We have several custom post types on our site (not thru custom press) we are running into a strange issue where if we have marketpress activated, one of the cpts dissappears from the left nav admin menu (but still appears in the upper new+ menu). When we deactivate mp the 3rd post type reappears.
The post type slugs are: trails, recipes, and reviews.
Oddly enough if I move the code for recipes above the code for reviews(in the post-types.php), then recipes appears, it I move it back down below then reviews appears. It's as if it is only allowing a certain # of cpts outside of marketpress.
Is there some sort of cpt conflict or limitation to the # of menu items within the marketpress plugin code?
We have several custom post types on our site (not thru custom press) we are running into a strange issue where if we have marketpress activated, one of the cpts dissappears from the left nav admin menu (but still appears in the upper new+ menu). When we deactivate mp the 3rd post type reappears.
The post type slugs are: trails, recipes, and reviews.
Oddly enough if I move the code for recipes above the code for reviews(in the post-types.php), then recipes appears, it I move it back down below then reviews appears. It's as if it is only allowing a certain # of cpts outside of marketpress.
Is there some sort of cpt conflict or limitation to the # of menu items within the marketpress plugin code?
Thanks for this great question and a significant item to bring up.
We are currently testing this out in our development environment, and I'm going to discuss it with the lead developer - to get a fix sorted for you asap.
Thanks again for bringing this up, and of course for being a WPMU Dev member, we'll get back to you asap.
I appears the MU support plugin sets the placement for their nav item overriding one of ours, so we realized if they can set theirs specifically... so can we! so, looked up the code for doing that, and updated our CPTs to show up in specific spots: 11/12/13/14.
So it's "fixed" but not ideal, the issue being, if another plugin comes along and forces to a specific positon that's already taken... one wins, one loses, so those positions may need to be updated in the future...
Responses (6)
Support Kangaroo — 7th February 2012 #
Greetings jzvestor,
Thanks for this great question and a significant item to bring up.
We are currently testing this out in our development environment, and I'm going to discuss it with the lead developer - to get a fix sorted for you asap.
Thanks again for bringing this up, and of course for being a WPMU Dev member, we'll get back to you asap.
Cheers, Joe :-)
Member — 7th February 2012 #
We are trouble shooting and think it might actually be related to the MU Support System plugin!
Support Kangaroo — 7th February 2012 #
Greetings jzvestor,
Thank you for letting us know that this issue may be a conflict with another plugin.
Please keep us appraised of your findings and we will keep at it on our end for final diagnosis/resolution.
Cheers, Joe :-)
Lead Developer — 7th February 2012 #
This can happen if 2 plugins use the same priority number for their menus. There are only so many, so you may need to adjust a plugin.
See the menu_position arg in http://codex.wordpress.org/Function_Reference/register_post_type#Parameters or $position in http://codex.wordpress.org/Function_Reference/add_menu_page
Member — 7th February 2012 #
I appears the MU support plugin sets the placement for their nav item overriding one of ours, so we realized if they can set theirs specifically... so can we! so, looked up the code for doing that, and updated our CPTs to show up in specific spots: 11/12/13/14.
So it's "fixed" but not ideal, the issue being, if another plugin comes along and forces to a specific positon that's already taken... one wins, one loses, so those positions may need to be updated in the future...
Long story short, it's NOT marketpress :)
Support Kangaroo — 7th February 2012 #
Greetings jzvestor,
That is great news that you folks have resolved this issue and thank you for letting us know.
Cheers, Joe :-)
Become a member