Hello- I did look and didn't see a similar issue...

I upgraded Token to the current dev yesterday. In my basic content type, I have a website Link field that is set to display as Title as link (default).

It has started displaying [title-raw] as the link text instead of the actual title. This is the display in all forms- as a node view, in a view list and in a panel.

It was working fine before the update. Other tokens appear to be OK; custom breadcrumbs for example is working fine.

Any thoughts?

Comments

mark lacroix’s picture

mark lacroix commented
Version: 6.x-1.x-dev » 6.x-1.13

Same problem here, since upgrading to 6.x-1.13, I get "[title-raw]" or "[date]" or whatever instead of the evaluated token, when used in a CCK link field. The only other place I use Tokens is in URL aliases, and they still work fine when creating new nodes, so it could be related to either CCK or Link (I also updated those modules at the same time as I updated Token).

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

This might be a duplicate of #825112: No tokens available ... at all..

mark lacroix’s picture

mark lacroix commented
Project: Token » Link
Version: 6.x-1.13 » 6.x-2.9
Category: support » bug
Priority: Normal » Critical

Actually, I was able to confirm that it was a problem with the Link module which was resolved when I downgraded to 2.8. It looks like that's also the case with the original poster, so I'm re-assigning this to the Link 6.x-2.9 issues page.

mark lacroix’s picture

mark lacroix commented
Title: Token displaying code- [title-raw] instead of title » Token integration: displaying code [title-raw] instead of title

**changed title**

Looks like a duplicate of: http://drupal.org/node/462538

webwriter’s picture

webwriter commented

Correct! This patch http://drupal.org/files/issues/link_462538.patch in http://drupal.org/node/462538 fixed the issue.

Thanks!

jcfiala’s picture

jcfiala commented
Status: Active » Closed (duplicate)

Okay folks, I'm officially marking this as a duplicate of #462538: "Allow User Entered Tokens" is required to be checked in order to enter tokens on the field settings page, but shouldn't be - as webwriter notes in item #5 above, you can go there for a patch.