I've experienced this problem intermittently and have not yet pinned it down exactly. When I edit a category, sometimes the menu items of sub-categories are disabled. I then have to go back to those sub-categories and click edit advanced settings, and re-select the parent item. Or I can do this from the admin->menu section.
Next time it happens I'll try to provide more info.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | Picture 8_1.png | 8 KB | ira42 |
Comments
Comment #1
kibik commentedSame problem. But are disabled each time i'm editing category.
Comment #2
ira42 commentedSame here. Have you guys resolved this by any chance? (or have any better idea of what's causing this?)
Even if I don't modify any of the settings and re-save the category, I get the following meesage (see attachment), and all of my existing category submenu items disappear...
Does this imply that the problem may be caused by pathauto?
Confused,
Ira
Comment #3
bdragon commentedCheck your container settings.
Is it set to breadcrumbs only?
Comment #4
ira42 commentedWell, I have the "Menu items within this container:" set to Enabled, and the "Menu items for assigned nodes:" set to "Enabled: Breadcrumbs only", which I believe is the right way to go in my case (I only want containers/categories listed in the menu, not individual nodes).
Still happening every time I modify a category. Is there something I should look for that would help narrow down the problem?
Tx
Comment #5
ira42 commentedUgh... It seems this is a known issue, and that there's no real workaround (as far as I can tell):
http://category.greenash.net.au/multiple_root_menus
See the last section, "Drawbacks"... Very bad news, and looks like after weeks of working with Category module, it's back to square one. Again.
Ira
Comment #6
JirkaRybka commentedThe category_menu module on 5.x have issues (more or less caused by the design, which in turn is forced by 5.x menu system), but I believe that changing menu items on node edits to be "in sync" is the whole point of category_menu, and therefore by design. You're not supposed to interfere by doing further customizations (however bad this might sound). Fortunately, 6.x is more robust in this regard, allows for selection of default menu per-container etc., so we're now definitely in better state than before. (See also [#http://drupal.org/node/481280] for another fixes proposed by me.)
Otherwise, this is one of *many* issues pointing out weird behavior and confusion related to auto-generated menu items on 5.x and below, which are now unlikely to be fixed in any way, because 5.x is hardly even maintained now, and the whole 5.x system gives little to no chance.
So, there's this big warning on Category project page - or a disclaimer - you need to read before downloading Category.
Closing this one (also due to >2 years of silence here). Feel free to re-open if needed.