They are empty when a node is created for the first time, but they works with bulk updates.
Could it be related to http://drupal.org/node/137669?

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Postponed (maintainer needs more info)

It seems similar.

What are your taxonomy settings for this node? What kinds of taxonomies are they? What weights? Etc.

Also, did you run update.php?

samuelet’s picture

samuelet commented

I've got drupal 5.3 and token 5.x.1.9.
Vocabolary options are all disabled (the default) except the request fileld and the content type assigned checkbox. It's weight is 0.
This vocabulary contains 11 terms, and they are not sorted with continuos weight (i mean the first is -8, then -4, then 2,etc).

Today i've tested the patch posted on token issue with this Pathauto setting for the type content:
[type]/[vocab]/[term]/[title]

The error is always an unaliased [vocab] and again an empty [term]:
/article/[vocab]/test instead of /article/auto/fiat/test.

greggles’s picture

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

I can't repeat this behavior.

Can you confirm if you ran update.php?

Also, run this query: "SELECT weight FROM system WHERE name = 'pathauto';"

samuelet’s picture

samuelet commented

Yes, i did it.
I've also reapplied token and pathauto last updates and log seems ok:

pathauto module
Update #4

    * No queries

token module
Update #1

    * UPDATE {system} SET weight = 10 WHERE name = 'token'

Atm i can't query directly the database, but, for the weight query, the dba module simply outputs:

weight
1
greggles’s picture

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

I've just done a fresh install based on 5.x-2.0-beta5 and still couldn't repeat the behavior.

Previously I had only tested this on sites where I had done upgrades from 5.x-1.x - now I've tested on a fresh install. I'm really curious how this bug pops up.

I'd really like to fix this prior to make 5.x-2.0 final. So, if you can indulge some more testing measures...

Start with a fresh site and install pathauto and just keep track of every step necessary to repeat the bug. Hopefully it should be 10 steps or less.

If you can't repeat the bug, compare the two sites and keep adding a step until it's possible to repeat.

samuelet’s picture

samuelet commented

As soon i can i'll try with a fresh installation. Just only a note:
With beta5 i get this errors for my dates:

You are using the token [dd-mm-yyyy] which is not valid within the scope of tokens where you are using it.

But i use [dd]-[mm]-[yyyy] and alias is correctly created.

greggles’s picture

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

Thanks. In general please open a new issue for each problem. I fixed the [mm]-[dd] problem which was related to http://drupal.org/node/184293 - I also discussed the problem/fix in that issue to keep this issue on topic.

samuelet’s picture

samuelet commented

Sorry for long delay, but i can't reproduce it with a fresh installation.
I could miss some configuration since the drupal site is in a production state and has a lot of changes from a fresh one, but at this point i think it's my configuration fault.

I remember that the database was manually utf8 encoded because of a mysql upgrade (old one was latin), but i don't know if it could be related to this bug.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Ok - I'll mark this as closed then.

If you can figure out how to consistently reproduce please do follow up.

Thanks.