I have installed pathauto 6.x1.2 module, but it is not working now. First it was working fine.

When I add any content I get url as node/100 instead of path that I have given through auto alias.

If anybody is getting the same problem and have solved the problem. Let me know.

CommentFileSizeAuthor
#7 pathauto.JPG57.45 KBnewbie66

Comments

amitnazare’s picture

Assigned: amitnazare » Unassigned
dave reid’s picture

Status: Active » Postponed (maintainer needs more info)

Did you check the 'Automatic alias' checkbox is checked on the node form? What URL alias patterns are you using for nodes? We need more information than just "it's not working."

willowwillow’s picture

I've recently updated to Pathauto 6.x-1.3 and have the same problem.
Auto alias is checked.
Anyone found a solution?

bishless’s picture

After upgrading to 6.x-1.3, I'm having a similar issue.

I'm using [termpath-raw]/[title-raw] for my node replacement pattern.

For content that already had a URL alias created by PathAuto, no amount of changing taxonomy terms will get the URL alias to change. We uncheck Auto Alias. Clear the path that was set. And recheck Auto Alias, then Save. Either the original URL alias sticks, or the lightest term in my taxonomy gets applied (incorrectly). However, for new nodes, the expected URL alias is being generated.

/frustrated

newbie66’s picture

i am also suddenly having this problem. when i edit node with auto alias checked the new alias is saved and appears in the current browser url but when i go to another browser window the url has reverted back to /node/# . has anyone had resolution of this yet?

greggles’s picture

@newbie66 - what is the alias that you expect to be created?

newbie66’s picture

StatusFileSize
new57.45 KB

hi and thanks. The alias i expect is the one it defaults to being the node title eg content/how-get-pregnant-fast-naturally (see attached). It used to work fine and i can't think of anything new i've done.

dave reid’s picture

Is your other browser window using a different language on your site? Is the browser on the node/x path and you're reloading or are you actually on a page that links to that node and looking at the link it creates?

dave reid’s picture

Status: Postponed (maintainer needs more info) » Fixed

As there has been no response after a month, I'm marking this issue is fixed. If you can provide more details or re-confirm this, please change the status field back to 'active'.

evelien’s picture

Version: 6.x-1.x-dev » 6.x-1.3
Status: Fixed » Active

I use the same replacement pattern and I am facing the same issue. New nodes is fine, autoupdate nodes without path doesn't work and editing old nodes with autoalias checked won't work.
For me it isn't a big issue, because there are only about 10 nodes to rename manually now, but I can confirm the issue (6.x-1.3)

greggles’s picture

@evelien what is your update action in "General settings" ?

dave reid’s picture

editing old nodes with autoalias checked

It's not clear if you tried re-saving these nodes with the autoalias checkbox checked.

dave reid’s picture

Status: Active » Postponed (maintainer needs more info)
evelien’s picture

Of course I was resaving them, otherwise nothing would happen :)
This was July, I'm not sure which of the 10 sites I was working on then was having this problem. Because it was a minor issue for me, I think I renamed these 10 nodes by hand.
It could be that the general settings - update action was the problem, not sure anymore.
If it happens again, (I'm working on a big site right now, not sure yet if I will run into this problem there), I will give more details.
Sorry!

dave reid’s picture

Status: Postponed (maintainer needs more info) » Fixed

Ok, if/when it happens again, please file a new issue with all the details. For now, I'm marking this as fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.