I'm not entirely sure if this is a bug, but it is a potential usability problem.

I recently changed the name of a cck date field ("oldfieldname"). It was used only in one cck content type ("event").

Going to the automated URL aliases settings, I receive, as expected, the warning You are using the token [field_oldfieldname-yyyy] which is not valid within the scope of tokens where you are using it. And under node path settings, the companion message appears under "Pattern for all Event paths" and "Pattern for all Event paths in English," also as expected.

But the same message appears for every content type, even where the field under any name is not used and where field_oldfieldname tokens were never specified to begin with. Saving as is clears the messages, but they are still misleading/confusing at first.

We are using Token 6-1.10 and Pathauto 6-1.dev on a fresh D6.2 install.

CommentFileSizeAuthor
#4 265948_pathauto_5x_6x_error_synchronizing.patch892 bytesgreggles

Comments

greggles’s picture

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

Thanks for the bug report.

You mentioned

I recently changed the name of a cck date field ("oldfieldname")

But when I go to the cck field settings I don't see how to change the internal field name. Where did you do that?

I'm testing with a cvs checkout of cck from today which seems to have a bug in changing the human readable label, so perhaps that is why I can't see this.

choster’s picture

choster commented

I had deleted the old date field and created a new one.

greggles’s picture

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

Sure - that I can see and in fact this bug is really easy to reproduce: insert a token that doesn't exist in the context like [asdf] and it happens. I fixed this in 5.x and it has popped up again in 6.x which I can't figure out just yet...

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Fixed
StatusFileSize
new 265948_pathauto_5x_6x_error_synchronizing.patch892 bytes

Well, this apparently didn't make it into 6.x even though it was added to 5.x.

So, I committed the attached fix.

Thanks for finding it, choster.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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