Traditionaly the Drupal interface uses <xxxx> in menu paths when referring to special items. That's the case with <front>. Some modules that provide special paths also work this ways (example: Menu First Child).

Using <xxxx> has some advantages:

  • It makes clear and stand out that the menu item is special in some sense, not an ordinary path
  • It avoid conflicts with existing paths (e.g. currently you cannot have a page at "/nolink" or "/separator")

So I think it would be good if the module used <xxxx> instead of plain xxxx.

Sorry for not providing a patch, but I'm just too busy now. I didn't look at the code yet, but I think that the change would be trivial. The biggest effort would be to create an upgrade procedure that change all e.g. "nolink" instances to "<nolink>" so that existing users can upgrade the module seamlessly.

Comments

henrijs.seso’s picture

henrijs.seso commented
Title: Consider using "<xxxx>" instead of plain "xxxx" in special items » Consider using <nolink> and <separator> instead of plain "nolink" in special items
Priority: Normal » Major

+1

Other modules and core already uses <front> and <firstchild> so using f. ex. <nolink> would be more understandable as well as probably resolve different conflicts.

gagarine’s picture

gagarine commented
Version: 6.x-1.5 » 7.x-1.x-dev
Status: Active » Fixed

Done for the D7 version. I'm not going to do a back port. Patchs are welcome for D6 but should have a update path.

Status: Fixed » Closed (fixed)

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