Menu Settings Fieldset missing when using Category in Drupal 6

The "menu settings" fieldset is supposed to be missing when using the Category module in Drupal 6. This is the main purpose of the new menu wrapper module: to remove that fieldset from the node editing form. The menu wrapper (included with the Category module) removes the menu settings fieldset from node forms, because this interferes with the autmatic menu link generation that the Category Menu module performs.

You can have your menu settings fieldset restored, by navigating to 'administer -> content management -> categories -> wrapper modules', and clicking the 'uninstall now' link for the menu wrapper. However, this is not advisable if you are using the Category Menu module - the menu settings fieldset is liable to override the automatic menu link generation that category menu performs, or vice versa.

So does this mean any clients using the category module simply can't edit the menus in any simple way? They have to go to the menu edit screen and enter the actual path to add menu items? I need the book wrapper module so that I can work with my nodes in views, and it is dependent on category_menu. What is the correct work-around? Put all my menu items into another container? Or what?

Thank you!

The book wrapper dependency is a problem, indeed, and a new one in 6.x too, but there's quite no-one to work on that.

Otherwise, category_menu module is supposed to generate menu links for you, so no need to create these manually. If you do (using the now removed fieldset), category_menu will then generate automatic menu item over that - and bingo, here comes a flood of bug reports as seen on 5.x version, where the manually created stuff wasn't kept properly. That's why the fieldset was removed (although I'm a bit unsure whether it's even necessary on 6.x, except that it possibly creates duplicate items?)

Of course, if you want both systems (manual & automatic) to co-exist on a per-container basis, you have a problem. But it's quite difficult to remove that fieldset in a dynamic way, because with non-required and distant-parenting containers it's impossible to tell which container(s) are going to affect the new node before the user submits the whole form with categories selection completed, and it might change later on node edits (and there might be more, not sure).

As for myself, I always considered that fieldset evil in general, because it suggests menu items for single nodes to posts authors. That's a way to horribly long menus and horribly slow menu handling. Overviews of posts in a tree is exactly what categories are for. It's also a matter of taste, obviously...

If you want the fieldset back, just comment out a tiny bit of code (now located in) category_menu.module, that does simply just unset() the fieldset in the node form, and notify your users better not to use it in containers with category_menu functionality enabled.

Unfortunately, category module is unlikely to ever reach a fully debugged state, due to lack of contributors.... :-(

Edit: If you meant editing the generated menu items through this fieldset, then no - these are completely different things and won't show up in that fieldset anyway. Basically, there should be no need to edit them separately, as they are generated straight from the node, reflecting it's title etc. Having them synchronized is the whole point. You should choose whether you want to maintain the items yourself, or to have Drupal do it for you, you can't have both for the same items, as that would be a conflict. If that's what you meant, not sure here...

Thank you so much for your prompt response! And also, thank you very much for helping me understand some stuff better!

Now I understand it properly, I like using the category_menu module for my menus better anyway. Because I can choose what content types are allowed to be put into which menus and such.

Thank you very much! I really like the whole category module. I hope that sometime in the near future I will be able to contribute something to it, as it is a very good module and was exactly what I needed. Thanks again!