Use proper menu link loading for node menu links [#295177]

I am not sure if this is a pathauto issue or a token issue. I'm pretty sure it's not an admin_menu issue.

Modules
Drupal - 6.4
Pathauto - 6.x-2.x-dev 2008-Aug-13
Token - 6.x-1.x-dev 2008-Aug-02
admin_menu - 6.x-1.x-dev 2008-Aug-09

Steps to Reproduce

Enable Pathauto
Go to admin/build/path/pathauto
Set the Pattern for all Page paths under node path settings to [menupath-raw]
Save Configuration
Create a new page

Title: Menu1
Menu link title: Menu1
Parent Item: Primary links

Save configuration

Link should be mysite.com/menu1

Go to admin/settings/site-information and set the homepage to node/1

Enable admin_menu

Go to node/1/edit

Click save configuration

Path is now the drupal icon path.

It seems when either pathauto or token looks for the menu path of the node it looks for node/1 and finds the admin_menu path for the homepage in the menu_links table which in this case is node/1 and link_title was the drupal icon image.

Comment	File	Size	Author
#11	295177-token-node-menu-load-D6.patch	3.15 KB	dave reid
#10	295177-token-node-menu-load-D6.patch	7.24 KB	dave reid

Comments

Comment #1

redndahead commented 14 August 2008 at 07:36

Here is the link to the pathauto issue: http://drupal.org/node/295179

Comment #2

redndahead commented 14 August 2008 at 17:30

Looking at this it may not be fixable. I think the issue is another menu item with the same path can be created very easily and for now you have to take the first result on your menu_links query. I think the only way to fix this permanently is to change core so that the node table gets an assigned mlid if a user saves a node that has a menu. Then you will be able to get a nodes associated mlid.

Does this sound about right?

Comment #3

redndahead commented 14 August 2008 at 19:48

Here is a link to an issue for admin_menu to use the absolute path instead of the relative one to avoid conflicts.

http://drupal.org/node/295476

Comment #4

sun

German

Karlsruhe

commented 17 September 2008 at 08:11

Version:	6.x-1.x-dev	» 6.x-1.11
Priority:	Normal	» Critical

Bumping to critical.

As far as I understand, Token does not limit the result set of path aliases to system generated ones, resp. items a user has access to. Under certain conditions, this may lead to a wrong behavior of the menu system.

Further information:
#279767: User counter is output on login page for anonymous users
#295476: admin_menu conflicts with pathauto
#303247: Menu Breadcrumb setting active menu to undesirable menus
#296534: Link paths are not unique

Comment #5

petertj commented 17 September 2008 at 08:37

subscribing...

Comment #6

sutharsan commented 26 October 2009 at 09:23

I can provide a tarball of a site with the #279767 error.

Comment #7

dave reid

he/him

English

Nebraska USA

commented 8 June 2010 at 03:45

Priority:

Critical

» Normal

Comment #8

dave reid

he/him

English

Nebraska USA

commented 4 July 2010 at 22:09

Status:

Active

» Postponed (maintainer needs more info)

Can someone point out where the problem is with token and where we can fix it? I don't understand from any of the previous comments how this is a token problem and not an admin_menu problem.

Comment #9

sun

German

Karlsruhe

commented 5 July 2010 at 12:23

Status:

Postponed (maintainer needs more info)

» Active

pwolanin described the underlying menu system/links issue at hand in #296534-1: Link paths are not unique

I think that Token needs to limit the db result set for menu* tokens to menu links that were stored by module = 'menu', i.e., manually created menu links. Something like that, at least.