can't edit nodes with aliases that start with same string as other aliases
| Project: | Drupal |
| Version: | 4.7.4 |
| Component: | path.module |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
I've come up against a bug with URL Aliases when two node titles start with the same string. This only seems to apply when you try to edit the node. I've posted an issue to the path module, but haven't gotten any response. Unless I'm the only one experiencing this issue, it seems like a rather serious bug. http://drupal.org/node/111775
Here is the scenario:
A CCK node type.
Pathauto enabled and set to create url aliases for node type with "something/something/[title]" as alias.
If the "[title]" has a shared string as another "[title]", you can't get to the edit page through the url alias.
Example:
My Pathauto urls for my node type are, "compass/site/[title]".
I have a node with a title "Seattle" and the url alias "compass/site/seattle" and the edit url alias as "compass/site/seattle/edit".
I have another node with a title "Seattle Center" and the url alias "compass/site/seattle_center" and the edit url alias as "compass/site/seattle_center/edit".
The URL alias for both these nodes works fine, but when you try to edit the second node, it can't resolve the url and defaults to the Drupal welcome page. You can get to the edit page fine if you use the normal node path: "node/478/edit".
Has anyone else seen this and are there any solutions?

#1
Just to follow up. It appears to happen only if the first string contains only that string that is apart of the second string.
So, "compass/site/seattle" and "compass/site/seattle_center" causes the edit tab to not work for the "seattle_center" node.
But, "compass/site/seattle_downtown" and "compass/site/seattle_center" would work fine because the first node title is not contained in the second.
It would be great if someone else could confirm that this is a bug? Or if it's appearing because of my theme?
Thanks,
Mike
#2
This version is not supported. Reopen or create a new issue if the problem exists in any recent version (version equal or above Drupal 5)