If a user can create a new node and pathauto is set to use [menupath-raw], pathauto fails to use menu item of a current node.

Example, pathauto-token used here is [menu-raw]/[menupath-raw]:

User creates Page C on menuitem B:

Menu A

- menuitem B

If user 1 creates new node, pathauto creates path: example.com/menu-a/menuitem-b/page-c as expected.

If some other user creates node (with full permissions to path, pathauto, menu and menu_admin_per_menu -modules), pathauto creates oddly this path: example.com/menu-a/menuitem-b-0, like if menu item for this new node were not yet present.

So, user 1 has no problems. Others can not create path properly at first, BUT with sufficient permissions they can update path to correct pathauto-setting using automatic alias -tickbocx.

I ran out of options trying to isolate if this is a permission related problem.

Comments

dave reid’s picture

Status: Active » Postponed (maintainer needs more info)

I'm guessing something with menu_admin_per_menu might be interfering here. What version of the Token module are you using?

rpsu’s picture

I'm using Token 6.x-1.15 (latest).

rpsu’s picture

Status: Postponed (maintainer needs more info) » Active
rpsu’s picture

I tried to alter module weight as well, but it did not resolve this error.

UPDATE `my_site_DB`.`system` 
SET `weight` = '0'
WHERE `system`.`filename` = 'sites/my_site/modules/menu_admin_per_menu/menu_admin_per_menu.module'
  • Giving Menu_admin_per_menu weight '-1' made menu fieldset disappear totally in example.com/node/add/page -form (with user without full menu administration permission, with some administer menu-name menu items). Apparently menu administration -module overrides menu_admin_per_menu -module permission modifications this way.
  • Giving Menu_admin_per_menu weight '1' did not resolve this either - the same example.com/menuA/menuitemB-0 -menupath just got back.
rpsu’s picture

Tested with Menu Permissions -module

The same issue continues with Menu Permissions -module (menu_perms).

Add node -form seems to work with module weight set to '1' (as modified in post #4), but menupath problem persist.

Tested with Delegate menu admin -module

The same issue continues with Delegate Menu Administration -module (delegate_menu_admin).

With module weight set to "1" user may set menu item, but menupath does not exist yet.

With module weight set to '-1' menu settings is not visible (apparently since menu -module overrides it).


Giving user 'create path' -permission or any other path or pathauto permission does not have any effect on this while any of these three modules are in use.

I could not find any other menu administration by role -kind of modules so there seems to be no solution for this? All I can think of is give some of my (trusted) user full administration menu -permission to go round this problem at this point.

Is there something I can do to help you (or more like my self...) with this?

rpsu’s picture

I decided to go round the problem by still using menu_admin_per_menu and adjusting my menu a bit structure. In pathauto instead of using preferred [menu-raw]/[menupath-raw], I use [menu-raw]/[title-raw]. It shortens url's a bit, but the site structure disappears from within menu.

If this issue gets solved some day, I'd be happy if you'd post solution in here as well. I've read some other issues like #333590: Node menu token fails (node grants not saved yet, menu access checking, oh my!) around menupath-raw -tokenas well so it seems to be a bit bigger issue than this my case.

Frederic wbase’s picture

Bumping, i have the same issue. Any progess?

Frederic wbase’s picture

Today i have updated to the latest version of pathauto en drupal 6.22 and the problem seems to be fixed.

rpsu’s picture

I can confirm this, it works. Thanks!

rpsu’s picture

Status: Active » Fixed
steven_kropp’s picture

Once I upgraded to Token 6.x-1.16 my menupath-raw stopped working...
I degraded to 6.x-1.15 and everything was fine
I am running the most recent version of pathauto (6.x-1.5)
any advice?
Basically, when a new node is created, NO auto alias is created, I have to force update or after the node is created, I have to go back to the page and check the create alias box, it by default now sets itself to NO ALIAS.

Like I said before, this all seems to be caused by the update to the latest Token Mod.

steven_kropp’s picture

Status: Fixed » Needs work

Should I start a new thread... I believe this issue to not be resolved?

dave reid’s picture

Status: Needs work » Fixed

@steven_kropp: Please start a new thread if you can confirm the behavior when using a fresh install of core and just Pathauto/Token. It may be another module conflicting.

Status: Fixed » Closed (fixed)

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