- This topic has 4 replies, 3 voices, and was last updated 4 months, 3 weeks ago by
Anh Tran.
-
AuthorPosts
-
March 16, 2023 at 8:14 PM #41044
AnLip
ParticipantHi !
I have never had this work correctly for ordering CPTs in the Menu. I always thought it didn't matter, but after almost two years using MB, I'm just surprised this hasn't been fixed. Am I the only one having issues with ordering of CPTs in the WP Menu ?
Whatever I do, at some point it all gets messed up. Some Menu items aren't even taken in account (such as Bricks Builder menu : it is selectable but nothing will ever get correctly placed below it).I am getting a little annoyed with this feature, I'd like delivered projects to look somehow how I want them to in the backend... but this is the 5th project that I'm not getting this to work (so I end up abandoning the idea of having a neat structured WP Menu). Am I the one not doing things correctly, or what is it ?
Take a look : [link not available anymore]
March 16, 2023 at 10:56 PM #41056Peter
ModeratorHello,
The menu position works correctly on my local site. But it can be modified by any plugin or theme on your site which also use the WordPress hook to add its menu and can rearrange the position then.
You can try to deactivate all plugins and leave Meta Box, MB AIO activate and switch to a standard theme of WordPress then check this issue again.
You can also read more about the default menu structure number here https://developer.wordpress.org/reference/functions/add_menu_page/#menu-structure
March 17, 2023 at 6:43 PM #41064ParticipantHello, thank you for getting back to me.
Menu order is secondary to all other priorities such as the choice of theme (Bricks), and the necessary plugins (nothing fancy), so I cannot have as a solution to deactivate or change my themes/plugins.
If MB ambitions to offer the possibility to change menu orders, I think it is up to MB to check that their function is compatible with other most important plugins and themes. The installed plugins in my install are nothing fancy and none of them have any function to move menu order around, so why would it conflict with what MB is set to achieve ? They only just place themselves in the menu (usually at the bottom, except for Bricks that takes a top-level position). And as shown in my loom video, it works, until at some point the items get mixed up... sorry, but it feels like the issue is coming from MB. Could you please check on your test site making sure a few common plugins are installed ?
Below my plugin list (+ Bricks theme)
- All in One Migration + FTP extension
- Automatic.css
- BricksExtras
- Font Hero
- HappyFiles Pro
- Meta Box
- Meta Box AIO
- motion.page
- Plaster
- WordPress Importer
- WP Grid Builder
- WP Grid Builder - Bricks
- WP Grid Builder - Meta Box
- WPCodeBoxMarch 18, 2023 at 6:17 PM #41085ModeratorHello,
What Meta Box does, in this case, is to support the UI to register the post type with the WordPress function
register_post_type()instead of using the code.
https://developer.wordpress.org/reference/functions/register_post_type/If you want to check the issue, you can register some CPTs with the code and with your plugins and with non-plugins activated on a staging site to see how it goes. It's not possible to check a conflict with any plugins on the internet and it is also beyond our scope of support of Meta Box which you can read more here https://support.metabox.io/topic/support-policy/
I hope that makes sense.
July 31, 2024 at 4:06 PM #46058Anh Tran
KeymasterHi AnLip,
After debugging, we found the bug and fixed it. This fix will be available in the next version.
FYI: technically, it's kind of an edge case with Bricks. Bricks register a top-level menu with position = 2, which is the same as Dashboard. In this case, WordPress will modify this value to a number like 2.12345, e.g. a float number. In Meta Box, we use integers for menu positions as WordPress recommends, but it won't work in this case for Bricks. So, in the update, we allow to use float numbers for menu position, and filter the menu to force WordPress to accept them (cause by default WordPress doesn't accept menu position = float for custom post types).
-
AuthorPosts
- You must be logged in to reply to this topic.