Under "update actions" in admin/build/path/settings I have selected "Do nothing. Leave the old alias intact", but when I go to an existing node and change its alias, the original alias gives me a page not found, so it appears to have been deleted after all. I get the same effect if I select the option "Create a new alias. Leave the existing alias functioning."

Comments

thoughtcat’s picture

thoughtcat commented

I've switched to version 6.x-1.5 and am having the same problem with that...

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Closed (works as designed)

That is core's alias functionality doing that - not Pathauto. If you change the alias from one to another, core's path.module deletes the old one. We can only control changes related to automatic aliases.

As such, I'm marking this as works by design.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Title: Original alias being deleted despite telling Pauthauto not to » Apply Pathauto's update action behavior with manual alias changes
Version: 6.x-2.0-alpha3 » 7.x-1.x-dev
Category: bug » feature
Status: Closed (works as designed) » Active

Hrm, I wonder if we should actually help 'alter' core's behavior here. Changing to a feature request.

nripoli’s picture

nripoli commented

Did this issue ever get resolved? I am responsible for updating content on an existing page, but I do not want the old alias to be deleted. If there are inbound links to the old alias, it is important the user does not land on an error page.

If I select the update action "Do nothing. Leave old alias", will the Pathauto feature work?

kishoresai438’s picture

kishoresai438 commented
Priority: Normal » Major
Issue summary: View changes
Issue tags: +Path Auto

Hi team,

This is my first post. I am selecting the "Create a new alias. Leave the existing alias functioning." option in Url Alias. But, It deletes the old alias name. can anybody suggest me on this?

mably’s picture

mably commented
Status: Active » Closed (outdated)

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.