Cat_menu: must use Advanced Settings to change location in menu system

This is only sort of a bug. I ran into this same issue. Category.module,v 1.100.2.17 2006/07/10 09:36:36

I did a new container with the default settings and it seemed to work fine after. Try these settings as a base.

Container Info:
Single Heiarchy
No checkboxes checked
weight 0, depth -1

Distant parents: This is what I believe the real problem was
- Unhighlight this. Make it only this container or unhighlight
and highlight others.
My setting is
and no other ones highlighted.

Category Menu Items:
Menu items within this container: enabled
Menu items for assigned nodes: enabled

See what those do for ya, lemme know if it helps.

Dang brackets - Here is what I meant -

Distant parents: This is what I believe the real problem was
:Root: - Unhighlight this. Make it only :this container: or unhighlight :this container: and highlight others.
My setting is :root: and no other ones highlighted.

(turn :: into lessthan and greaterthan brackets)

This bug might be related to this one: http://drupal.org/node/48178

We need to get to the bottom of this. It kills me, because I have like 50 categories / subcategories that I need to change from time-to-time.

In my opinion, about 95% of category_menu related bugs are probably bugs related to the underlying menu system and the horrible menu_otf module which was integrated into core in 4.6.

Marking this as master bug for the "Must use Advanced Settings to change location in menu system" user interface issue.
List shortly, standby.

Hmm, having trouble telling this apart from menu_otf bugs. Cancelling consolidation. Will look into http://drupal.org/node/18351 instead.

The bugs do sounds similar. We are experiencing all this with two of our dev sites and its one of the things holding us back from Categories.

My thoughts (without delving into the code) is that there is probably a missing node_load somewhere so when you update Drupal doesn't know enough about the node and its location/info to recreate the menu item.

changing title to the one suggested by bdragon, and make it clear it refers to category_menu and not to core category.module. Sorry, no idea of what could be the cause, category_menu.module definitely needs bug fixing.

marcob, bdragon, I wonder if this is a cat_menu 'bug' at all.

According to Jaza, the correct way for the original poster's situation to be resolved would have been to change the default menu at administer>>settings>>category>>menu item settings.

Please see http://category.greenash.net.au/node/17#comment-7

I agree, though, that it would be very handy to do it from the Advanced settings page without messing around with default menus where people could forget to do it.

So, does this make this less of a cat_menu bug? The advanced menu settings are after all injected into the node form by the core menu system.

Someone identified the cause of the bug in the issue linked at #6 of this thread and also posted a patch.

Does this help solve any cat_menu related bugs?