Pathauto is creating aliases based on old path settings and is creating duplicate url aliases. This is seriously damaging my community where users are creating nodes but are seeing older nodes instead. I've been dealing with this issue for a long time now. Pathauto is not obeying the current path settings I have set for it, it's still using path settings that I've removed.

Comments

Dave Reid’s picture

Category: bug » support
Priority: Critical » Normal

Can you maybe explain in more detail what the problem is? Are you using Strongarm?

sp09’s picture

There's not much more detail to give. It uses old paths for new node paths instead of creating a fresh new path. So when you click on the new node it shows up as an older node in full node view because path auto didn't create a new path for it. So instead of the user seeing their node they see another user's node which is embarrassing to site and a bad site experience for the user. No I don't use strongarm.

modrar’s picture

I am also having this exact same issue.

Version 6.x-1.5
Not using Strongarm.

alar’s picture

Did you change any of the settings in Automated alias settings / General settings?
There is an option to
* Do nothing.
* Create a new alias. Leave the existing alias.
* Create a new alias. Delete the old alias.

Is the Automatic alias box checked when you create or edit content?
* Automatic alias
An alias will be generated for you. If you wish to create your own alias below uncheck this option.

alar’s picture

I was having similar troubles a few weeks ago. It started with a White Screen when I was doing a bulk generate.
I had never noticed the setting - "maximum number of objects of a given type to alias in a bulk update" - defaults to 50. Reduce the number to prevent white screen.

Egads 50? That's not many, so I ran bulk update several times. Are you running bulk update again and again?

darksnow’s picture

I was having this issue and perhaps I've found the cause, and a work around.

I created a few threads to create two named "test" which worked fine, the latter being called test-0, then added one called "sigs" which exists in the database already, this caused the conflict. My new thread, which should have been called sigs-1 since sigs-0 and sigs exists, was created as sigs. Clicking on the new thread then, correctly, took me to the thread already called sigs so I never got to se my new thread.

Digging in the database I found that paths generated by the system when I imported the old forum, have a language code of "en" against them while new ones, for some reason have "und" for undefined. The import was done by he phpbb2drupal module but the URLs were generated after the fact using the bulk update, so the import is not really relevant here, just mentioned for completeness.

It turns out the alias system can created an alias per language so when looking for existing ones, it doesn't seem to check anything that doesn't match the language code, and therefore misses some existing aliases.

I've manually updated the database to use the same language code throughout that table and this issue should hopefully be resolved. Since it's inconsistent it's difficult to test, but my sigs test above worked after update so I think I've found the culprit.