Because this module does not offer the same menu allocation service as the core node system, any paths created by it are automatically stored against the Navigation menu.

This basically means that *even as UID1 ("super admin")* you CANNOT see or alter these menu items. Turning off the menu paths and trying to assign these manually also fails.

Bottom line is, menus need doing differently, or assigning different permissions on the callback - as far as I can tell.

Comments

momper’s picture

momper commented

+1

momper’s picture

momper commented

does somebody knows how to move it in the db to primary-links as a fast workaround?

thanks momper

momper’s picture

momper commented

for some people this maybe is an trivial problem - for others it's again a waste problem, of a module development that does not follow the basic rules of drupal. is there a special technical reason for this?

cyberswat’s picture

cyberswat commented

@momper - if you want to submit a patch feel free and it will be considered.

momper’s picture

momper commented

only a workaround: give anonymous user the permission to manage menu - change - deactivate permission again ...

and no - i'm not a developer and yes - i would prefer strict rules for developers for publishing modules

cyberswat’s picture

cyberswat commented
Status: Active » Fixed

The module was using the menu system correctly, but I appreciate the feedback. Enhanced AAR to allow the user to specify a parent menu when designating a path using the AAR admin. Also modified the access callback to allow the menu item to show up on the admin/build/menu pages ... previously it was not showing because an authenticated user can't see pages like the user signup page. Now you should be able to control the exact placement of the menu item by using the AAR admin to set the parent menu and then core menu pages to control the position in that menu. I'll have the tests in place to support this soon.

FYI ... this required a schema change so you'll have to completely uninstall and reinstall.

http://drupal.org/cvs?commit=250206

niklp’s picture

niklp commented

But there's no uninstall hook :/ option to uninstall from the ui. Does one have to do that manually?

cyberswat’s picture

cyberswat commented

I think we squared this away over irc. Added the db alter statement in as a an update hook so that people don't have to do a complete uninstall and reinstall between dev versions.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.