After upgrading to newest dev version, urls to users blogs changed to look like: blog/%5Buser%5D/6778. It does not generate actual user's name or user's id for the url, but literally puts %5Buser%5D or %5Buid%5D. How can I fix this?

Comments

Boinng’s picture

Boinng commented

I'm seeing the same - the [user] tag in blog addresses isn't being translated, the link is just being set (in my case) as blog/[user]/title-of-the-blog.

yngens’s picture

yngens commented
Title: Wrong URL generation: blog/%5Buser%5D/6778 » Wrong URL generation: blog/[user]/6778

Actually, I have brackets like [user] in my case too. I used ASCII code just because it shows in browser's address field. Changing title.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Have you always had this problem or does it seem to be a regression after updating to a more recent version?

Also, what version of token module are you using?

Thanks.

yngens’s picture

yngens commented

This happened after upgrading to the latest version. Before URL would be generated fine.

Pathouto.module's first line shows:
// $Id: pathauto.module,v 1.44.4.27 2007/09/06 18:17:41 greggles Exp $
Token.module's first line shows: $Id: README.txt,v 1.1 2006/12/31 01:41:50 eaton Exp $

Maybe what is written in taken.module's changelog can give a clue to the problem:

2007-August-15:
[menupath] token no longer includes the top level.  If you need the previous 
	   behavior please use [menu][menupath] to get the same effect.

Before 2007-August-15
Lots of stuff happened before we had a CHANGELOG.txt.
greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Token.module is 1.1?

Please update that to the 5.x-1.x-dev release.

yngens’s picture

yngens commented

greggles, it is actually 5.x-1.x-dev of 2007-Aug-24.
the modules first line shows: // $Id: token.module,v 1.5.2.9 2007/08/13 16:01:25 greggles Exp $

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Good and when you say "updating to latest version" which version had you been using? Just 5.x-1.x?

The reason I ask all this is that I can't reproduce your problem in two different test areas. One is using a 2.x-pre-beta version of pathauto with token5.x-1.8 and the other is using the most recent 2.x-dev with token latest dev.

Boinng’s picture

Boinng commented

I've just updated to the latest dev versions of both Pathauto 2.x and Token, and I'm still seeing the same problem, sorry!

Boinng’s picture

Boinng commented
Status: Active » Closed (works as designed)

Solved it! There's obviously been a change between the old 4.x version I was using and this new 5.x, but while my settings had retained "blog/[user]/[title]" as the template for Pathauto, [user] isn't actually a valid tag for the node path settings anymore - it's been replaced by [author-name]. Although, confusingly, [user] is still valid for the standard blog path settings.

So for the blog path, you'd still use blog/[user], but for an individual blog entry (under node path settings) you'd use blog/[author-name]/[title].

So this isn't a bug as such, but it may be something that needs highlighting to upgrading users - or, even, automating? Ideally, any reference to [user] in the existing node path settings could be converted to [author-name] as part of the upgrade?

yngens’s picture

yngens commented
Status: Closed (works as designed) » Active

i did hope i would find solution here. now i am really confused. i am sorry but i did not pay attention which version of the module it was before upgrading. probably 5.x-1.x as you suggested. and it is strange you can not reproduce this issue - double checked all the settings and i do believe the problem is in the latest version of the module. i can send you an address of my site with access if you are willing to take a look.

yngens’s picture

yngens commented

Boinng, thank you very much! It solved my problem. Please ignore my previous message since I started it and then was distracted with something and ended up submitting couple hours later even without noticing that Boinng had already submitted right solution to the issue.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Closed (duplicate)

http://drupal.org/node/143295

Please see that issue - this is a known problem.

If one of you could take a stab at writing an upgrade document that would be really helpful. I've forgotten many of the things that are "gotchas" in this process which are obviously much more noticeable to you ;)

Thanks!

yngens’s picture

yngens commented

greggles, i would contribute with pleasure, but my english is far from perfect. i believe documentation should be done by native speakers.