Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.After updating the module, and checking the settings-page in admin, i'm confronted with the following notices...
* You are using the token [vocab] which is not valid within the scope of tokens where you are using it.
* You are using the token [term] which is not valid within the scope of tokens where you are using it.
* You are using the token [title] which is not valid within the scope of tokens where you are using it.
* You are using the token [title] which is not valid within the scope of tokens where you are using it.
* You are using the token [title] which is not valid within the scope of tokens where you are using it.
* You are using the token [title] which is not valid within the scope of tokens where you are using it.
* You are using the token [title] which is not valid within the scope of tokens where you are using it.
* You are using the token [title] which is not valid within the scope of tokens where you are using it.
* You are using the token [catpath] which is not valid within the scope of tokens where you are using it.
* You are using the token [catpath] which is not valid within the scope of tokens where you are using it.
* You are using the token [catpath] which is not valid within the scope of tokens where you are using it.
* You are using the token [user] which is not valid within the scope of tokens where you are using it.
If I simply ignore them however, my aliases still work fine...
I'm using a structure like this:
content/[vocab]/[term]/[title].html as a default pattern,
manual/[title].html for book-pages (since it's only used for the manual),
faq/[title].html for the FAQ-module, etc, etc.....
Is this a booboo, or have I actually got it wrong? ;)
Comments
Comment #1
gregglesThanks very much for this report. That new warning system is one of the bigger changes in this version and I assumed it would have problems, but I wasn't sure how.
You should be using the -raw tokens. Did you get warnings about that as well? Also, the system adds a description to the fields that it thinks are wrong - though it currently doesn't tell you what's wrong with them - I guess I could try to make that part of it smarter.
Can you paste all of your patterns and settings? You can get them by running this query:
Select * from variable where name like 'pathauto_%';
Comment #2
gregglesComment #3
gregglesNo response so I assume that it was a doc/configuration issue.
Please let me know if/how I can make the changes more obvious or respond with your settings as requested in my first comment.
Comment #4
Alex Regenbogen commentedSorry Greggles for the late respond... have been busy doing my regular work instead of playing around with all the fun thingies of Drupal ;)
I just grabbed the latest 2.0, and when I use the -raw tokens, things work like a charm, so you last reply was completely correct, I should have RTFM-ed a little better... ;)