New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WordPress menu system enhancements #726
Comments
Needed by the next theme. |
Another RT member with the same issue here http://www.rockettheme.com/forum/wordpress-theme-fluent/274903-menu-issue We really need to get this resolved IMHO |
I'm sure it's related. When I try and create multi-columns or generally change the order of things nothing saves. I'll save my changes in the Menu Editor, browse away (to the Outlines tab or something) and when I come back everything, or 90% of my changes at least, have reverted. I'm sure I'll eventually get there by writing the menu.yaml file myself but I wanted to make sure this behavior was included in the fix. I did have child items that I made parents which may be part of my issues, as described by others here. |
For what it's worth I notice pretty strange behavior in how things are saved in the [menu-name].yaml file: --sometimes items don't save an Object ID, but they still seem to work... the Object ID seems important to me though, no? |
3 years later: Any idea if that gets fixed? |
We have a large development in progress which requires use of this menu system, should we assume this bug cannot be fixed? |
I took yet another deep look into this issue and I have found a fix for the issue. It will take some time to get it fully fixed and tested, but I'm hopeful that it will finally be fixed to the next version (5.4.26) which should be out within 2 months. You can see the progress in https://github.com/gantry/gantry5/tree/feature/wp_menu branch. Right now the branch has the logic to save all our extra data into the menu items, but only menu item specific data is loaded from the database. This means that ordering, columns and particles are not yet loaded from the new DB storage. |
UPDATE: Make that Gantry 5.4.27 as there was a regression bug in 5.4.25 which needed a quick patch. |
Will the new DB storage for the Menu address this issue? |
Regarding to WPML menu issue, I don't think that synching menu particles to the database fixes the issue, but I have not tested it yet. As an update, I've made great progress on fully utilizing WP menu items in the database inside Gantry menu and its manager. There are still some minor issues that I need to fix as well as a decent amount of testing needed, but the implementation looks to be working great in most parts. |
I highly recommend doing the following... Whenever a person is modifying the menu - create a temporary menu with what is being created. Erase the core menu - and replace with the new menu once saved. The only way I resolved this was by erasing the YAML file. |
Closing in favour of #2473 |
I was having the same issue reported with menu items in a Joomla site - were the improvements made just to the WP branch? Should I open a new issue for Joomla? |
I'm going to look into Joomla and Grav next. |
This was postponed to be added after release, but I cannot find ticket for that so I'm going to make a list of items that Gantry 5 WP menus still needs to get done.
The text was updated successfully, but these errors were encountered: