Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.In the attached screenshot, I changed the parent of all the child containers and categories of 'News', since I wanted to delete 'News' prior to changing it from a container to a category.
As the screenshot shows (the next link points to events, which is the next container), I have moved all the child containers and categories, but category_menu still points to the 'KCRDS News' category, although its parent has already been changed.
Refreshing the browser many times did not help. I opened IE afresh and pasted in the url, with similar results. I have noticed the same issue on other occasions also.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | category_menu_update_issue2.gif | 6.61 KB | venkat-rk |
| category_menu_update_issue.gif | 4.75 KB | venkat-rk |
Comments
Comment #1
venkat-rk commentedI just had this issue confirmed in a strange way.
By mistake, I had enabled the 'Menu items for assigned nodes' for a hidden container, so when I created the post, it got added to the menu ('this is a test post' under 'News' in the attached screenshot). So, I disabled that setting, saved the changes to the hidden container, went to the node, edited it and saved the changes.
But the node link did not disappear from the menu. I had to manually disable it admin>>menu
Comment #2
inforeto commentedUsing the 'Menu Settings' entry appear non-functional.
Fortunately the link to advanced settings conveniently takes you to the working menu module options for that entry.
Comment #3
inforeto commentedIn addition, if the menu item is manually removed and you edit the container the menu entry regenerates on its default position.
If the menu item is moved to another menu the changes dissapear.
Perhaps a piece of code can detect an existing item and abort creating a new item.
Comment #4
venkat-rk commentedThanks inforeto for reminding me aboutthe advanced menu settings. But, I am changing the version back to 4.7.0 because although not critical this bug originated is unresolved for that version and gives admins a bit of a hard time.
Comment #5
JirkaRybka commentedIt was all buggy on 4.7.x, yes, but now it's 3 years old issue with no activity, and 4.7.x is just history... Closing.