purl/part1/restofalias
if purl is 'part1', it activates the purl at part1/restofalias (the alias without the purl).

if purl exists that equals 'part1', visit part1/restofalias that is not associated with that part1 purl, it strips of blog and redirects to restofalias and 404s, cause restofalias doesn't exist.

Real word case: spaces/purl/spaces_og setup, blog/nid/title, create community blog.

Patch attaches addresses pathauto, with a hook_requirements catching there's a token at part1 and warning that can't predict aliases.

Setting needs work to add a warning at pathauto urls also and for addresses existing aliases (manual aliases) which would also cause issues.

CommentFileSizeAuthor
#3 conflict-between-aliases-and-purl-1016474-D7.patch1.02 KBwebflo
#1 1016474_purl_aliasconflict.patch3.89 KBhefox
purl_pathauto_conflict.patch2.8 KBhefox

Comments

hefox’s picture

hefox commented
Status: Needs work » Needs review
StatusFileSize
new 1016474_purl_aliasconflict.patch3.89 KB

Could use even more checking, specifically at alias admin section, but good for review now I think. Adds in checking alias table and checking nodes path variable on save for potential conflicts.

socialnicheguru’s picture

socialnicheguru commented

I am wondering if this is the same

I have an og with node id = 1
i have purl enabled and path configured
the purl path for the og at node id 1 is mygroup

when I goto the url

http://mysite.com/node/1 I get
http://mysite.com/mygroup/node 1 and this is a 404.

I tried your patch and this was not solved

webflo’s picture

webflo commented
StatusFileSize
new conflict-between-aliases-and-purl-1016474-D7.patch1.02 KB

Patch for purl 7.x-1.x-dev