ProsePoint Express: hosted newspaper website content management software

Problem with URL aliases

3 replies [Last post]
Willow
User offline. Last seen 2 years 26 weeks ago. Offline
Joined: 01/03/2009
Posts:

Hi beng,

Adding a new story with the title of a previous story seems to be causing some problems.  The behavior of pathauto seems to be to assign the new article the base alias (e.g. "my-series") and then append numbers to the aliases of the previous articles (e.g., "my-series-2") with the same title.

This is fine, but it causes a problem with search indexing.  If I search for a word that appears in "my-series-2" (the older story) in the above example, search correctly displays the node title and excerpt text but links to "my-series" instead of the new, changed alias "my-series-2".

Basically, search indexing is not taking account of the updated alias.  Any ideas what to do about this?

Willow
User offline. Last seen 2 years 26 weeks ago. Offline
Joined: 01/03/2009
Posts:
On further investigation, it

On further investigation, it looks like the problem is actually with pathauto failing to check for duplicate aliases.

I have two articles with the same title, and pathauto is assigning the same alias.  Even after editing each story, unchecking auto alias, and re-checking auto-alias, it still wants to give them the same alias.

Hmmmmm...

beng
User offline. Last seen 6 days 16 hours ago. Offline
Joined: 27/02/2009
Posts:
Maybe change your pathauto pattern to insert a node id?

Hi,

Maybe change your pathauto pattern to insert a node id? That would guarantee aliases will be unique.

ie. on .../admin/build/path/pathauto, change Pattern for all Story paths: to something like story/[nid]/[title-raw] ?

Willow
User offline. Last seen 2 years 26 weeks ago. Offline
Joined: 01/03/2009
Posts:
Yeah I might end up doing

Yeah I might end up doing that, but this is just getting curiouser and curiouser.

I can't figure out why pathauto insists that these two stories have the same alias!

I've removed auto-aliasing from both stories and re-enabled it one at a time... same result!