Closed (outdated)
Project:
Taxonomy Menu
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Apr 2010 at 21:06 UTC
Updated:
11 Mar 2016 at 14:59 UTC
Jump to comment: Most recent
Comments
Comment #1
hass commentedThe main issue here seems to be - if the menu is cluttered (and this happens to me) the regenerate all does not fully clear the menu items and regenerate them from scratch. I cannot say how and why this happens now, but it happened. As a workaround I managed to delete the menu (with it's "system generated" items) and recreated it. This deleted the orphaned menu items.
Comment #2
hass commentedComment #3
dilari commenteduhm...did you figure out how solve it? Other than the work around I mean ? Sure at start the work-around is fine, I guess, but how to deal with it when the site has grown and some things are deleted ? You wouldn't want to delete en recreate the menu then
Comment #4
hass commentedNot yet, sorry
Comment #5
indytechcook commentedUninstalling taxonomy menu (not just disabling) will delete all menu items created by taxonomy menu.
Alternatively, you can run this sql statement:
Comment #6
xl_cheese commentedI'm running into the same error. I'm trying to get a feel for how to create the taxonomy heirarchy and put it into a menu. Each time I recreate the menu there are some dulicates left behind and or created. Perhaps because I'm switching the options around when I regenerate the menu.
I found I have to do the same work around to fix it which is to start from scratch.
Comment #7
indytechcook commentedTry the latest dev.
Comment #8
xl_cheese commentedI still get duplicate menu items when I make any changes to my taxonomy vocabulary.
Comment #9
varver commentedTo delete a menu item which doesn't have the delete option (i.e. is orphaned, after deleting the associated taxonomy term), you can try visiting the 'delete' page of this item by hand.
In the 'List items' page of your menu, open the edit page of the (un)desirable item. The URL will be something like
http://example.com/admin/build/menu/item/830/edit
(As you can tell, I'm using clean URLs)
In the address bar of your web browser, change the '/edit' part with '/delete'
(e.g. http://example.com/admin/build/menu/item/830/delete )
and press enter. You will be asked to confirm this action.
Regards,
varver
Comment #10
hovel commentedvarver, Verry nice. Thank you.
Comment #11
verta commentedThank you for this tip - unfortunately I had so many orphans, it was faster to uninstall it.
Comment #12
peter.torok commentedThank you, thank you, thank you!
I have a good number of "loose editors" who mess up my neat taxonomy menu - weekly... :)
Comment #13
indytechcook commentedVery sorry about these orphans caused by bugs.
Comment #14
spgd01 commentedsubscribe
Comment #15
palmaross commentedCuriously, but visiting the 'delete' page lead me to the message 'you do not have access to this page', though I am the user#1 and I can edit all admin menu items ... But clicking on 'reset' removes orphaned items from admin menu!
Comment #16
herb_miller commentedI had the same problem as #15 when trying to do #9
I noticed that when I browsed the menu_links table using phpMyAdmin the module name for the items that could not be deleted was 'system' and for those that could be deleted it was 'menu'.
I used this query to check which items were affected.
so to re-enable the 'delete' link I ran
I was then able to remove the rogue menu items using the menu UI.
Also note that when I used 'reset' (during earlier investigation into the problem) the menu items switched from whatever menu they were in back to a previous menu.
Comment #17
visitor82 commentedSheer genius varver, thanks
Comment #18
dstolComment #19
hass commentedComment #20
rjdjohnston commentednice, thanks
Comment #21
khuramhb commentedChanging module from system to menu as mentioned in #16, works. After changing system to menu for the links in the table menu_links changes "reset" option to "delete". Thanks
Comment #22
hles commentedI think we can close this issue, all the menu links created by Taxonomy Menu belongs to the Taxonomy Menu in the last D6 release of the module and users should able to delete them. Please do re-open if that's not the case.
Comment #23
hass commentedWhat patch has been committed to get this bug fixed?
Comment #24
hles commentedWell, the bug was found in 2.7, now the latest version is 2.9 and we are 2 years later, so there was code commited. Could someone make this bug happen in version 2.9 as well ?
Comment #25
hass commentedThis bug was never fixed. Time does not fix bugs.
Comment #26
hles commentedI don't really see how being rude fix anything either. Time is not the matter; once again, there have been 2 new releases since the bug has been discovered 2 years ago, and I think it is fair to ask if someone have had this bug on the latest release of Taxonomy Menu.
Comment #27
hass commentedNothing rude, just the hard realities :-). As I already said, indytechcook and nobody else was not able to fix the issue. In 2.9 it is for sure not fixed. I'm running without automatic menu item updates for about 2 years and rebuild the menu from time to time manually. This is still a major problem :-(. Would be great to get it fixed.
Comment #28
knic commentedSame problem, and quite a few others I'm afraid, here on latest 6.x-2.9+15-dev.
I always have to remember to tread carefully and create database dumps before changing anything in my vocabulary menu settings. Things swivel around all over the place. I just managed to zap all my menus completely. Gone. Primary links don't exist any more. And that was after selecting the add /all to end of elements with children. This doesn't work (could we get it removed?). When I disabled it again, menu was rebuilt (another bug, I think, because rebuild was not selected) and everything went puf! Oh well.
My next step is to reload a backup and try to document these behaviours to see if they are consistent.
Comment #29
dstolThe Drupal 6 version is no longer supported