I am using Rules to adjust breadcrumbs based on cck node references for a custom project system. This was working fine in beta4, but has broke in beta5: the tokens for the loaded node are no longer working.

I confirmed using the debug output that the node is being loaded correctly (the CCK token works), and I can use user tokens in the breadcrumbs, but the tokens for the loaded content are never replaced.

It might be related that "Load content" variables are staying across multiple rule sets, each set shows the "Load content" variables for all others.
In each rule set, I used the same name for the loaded content. I tried changing the name on one of them, but it still didn't work. Upon trying to change it back, I got "This variable name is already in use" (although this is the only variable defined within the current set).

Marking this as critical, as it destroys the usefulness of loading content.

Comments

RoboPhred’s picture

RoboPhred commented
Title: "Load project" variables existing across rule sets. » [node:*] token returning empty strings

Did some more experimenting, it looks like the root cause for my specific issue is that the [node:*] tokens are returning empty, although the php $node variable still works).

I will make a new bug report for variables carrying over, as it is not related to this.

RoboPhred’s picture

RoboPhred commented
Title: [node:*] token returning empty strings » tokens returning empty strings

It appears this is not limited to the node token. When I replaced the "Load content" id from [node:nid] to echo $node->nid , the loaded content's tokens all return empty, and the loaded content's php variable returns valid values.

The token module continues to work properly with pathauto.

RoboPhred’s picture

RoboPhred commented
Version: 6.x-1.0-beta5 » 6.x-1.x-dev

This also happens in dev as of 2009-Mar-07

RoboPhred’s picture

RoboPhred commented

Still happens on a new website, so it [probably] isn't a module clash.

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented
Component: Rules Engine » Provided module integration
Category: bug » support
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

Have you tried with DV version of token?
What is the token syntax you are using - are you using Rule's syntax (e.g. [node-updated:title]).

RoboPhred’s picture

RoboPhred commented
Status: Postponed (maintainer needs more info) » Active

Hm, just noticed the note about the dev version of tokens. I had it once, but replaced it upon prompting from the updates module.

RoboPhred’s picture

RoboPhred commented
Status: Active » Closed (fixed)

Right, that got them working again.

I couldn't figure out what was ment by the entry on tokens in the FAQ, and somehow completely missed the mention on the project page...

mitchell’s picture

mitchell commented
Component: Provided module integration » Provided Module Integrations

Updated component.