Title says it all.

I want to remove the Primary and Secondary Links and I thought that was the purpose of the settings in "admin/build/menu/settings" and "admin/build/themes/settings", but apparently they did nothing.

If I navigate to "admin/build/menu" the Primary and Secondary Links menus are still there and it won't let me delete them. Also if I try to add a new node it will still let me choose Primary and Secondary Links as the menu parent.

I do everything I can to make things intuitive and user friendly for my end users and having 2 menus with cryptic names available to choose from is neither intuitive nor user friendly.

I want them gone! :)

I guess I've never encountered this problem before because I've usually just renamed the Primary and Secondary Links to menus of my own, but this time I created and populated a few menus from scratch. And I don't want to have to delete my menus, rename Primary and Secondary Links and manually transfer my menu elements to the renamed menus.

Thanks.

Comments

drawk’s picture

The theme settings are to turn on and off the display of the primary and secondary links, not to add or remove them entirely from the system.

If I understand you correctly, you want to remove reference to these so that they aren't exposed to the people who will be maintaining the website. (You said end users, but I don't see why the actual visitors and users of the site should have the permissions to add menu items at all ..). If you want to hide these items entirely, you may need to do so through a form_alter or at the template level.

drawk’s picture

Actually, I just stumbled across this module in another thread: http://drupal.org/project/ctm

This will allow you to remove primary and secondary links as menu options from the node submission pages per content type. Check out the screenshot.

twiik’s picture

End users, was poorly worded. :) Administrators and editors, yes.

That module actually worked perfectly, but sadly the Hierarchical Select module, which I'm also using to make things easier to use, didn't respect respect the disabled menus and showed them anyways.

Guess I will have to use one of them or try to make them work together.

We will see.

Thanks for your help.

Øyvind Strømsvik
Tech lead | Frontkom AS
https://frontkom.com/

drawk’s picture

Glad it worked .. or sort of worked :)

Sometimes experimenting with module weights can help with this sort of thing. You'll have to do this directly in the DB (the system table) as there is no interface for it. Try setting the weight for the ctm module to a higher value like 10 and it may solve the incompatibility issue.

ecmm2000’s picture

I'm looking for a solution as well as you can I publish here.

Eduardo Moreira
Links Patrocinados