I see the following warning in the status report after updating Workflow 7.x-2.3 to 2.4:

Tokens Problems detected

The following token types do not have any tokens defined:

$info['tokens']['WorkflowTransition']
$info['tokens']['WorkflowState']
$info['tokens']['Workflow']

Comments

johnv’s picture

Status: Active » Postponed (maintainer needs more info)

I cannot replicate this. I can understand the message, but it should be gone after flushing caches.

johnv’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I guess you have found an answer to this question.

olafski’s picture

Status: Closed (cannot reproduce) » Active

I get the same warning as described by moep (not after an update of the module but using a fresh installation of Workflow 7.x-2.4). And there is only one Workflow related token available in the token list on admin/help/token: [WorkflowField:last-transition]

When I activate the Entity tokens module, the message disappears, and the Workflow related tokens are visible at various places. Nonetheless they don't work for me. I tested tokens like [WorkflowField:last-transition:comment] or [current-user:last-transition] in a core action system message which is triggered by a workflow status transition on a node.

kcannick’s picture

Same issue. Tokens don't work in RUles or actions when sending emails.

one_hoopy_frood’s picture

This appeared for me after updating to the current DEV versions of TOKEN and WORKFLOW. (I deleted the entire directory before upgrading the modules and I ran updates)

Token 7.x-1.5+4-dev (2014-Jun-19)
Workflow 7.x-2.5-beta1+9-dev (2014-Nov-10)

To fix it, I enabled Entity Tokens. Warnings went away. Are those tokens working? I don't know, I don't have any rules based on them.

Now, why that may be I'll leave to the gurus.

  • johnv committed 04f624a on 7.x-2.x
    Issue #2304875: Fixed Status Report Tokens Warning when entity_token not...
johnv’s picture

Title: Status Report Tokens Warning » Status Report Tokens Warning when entity_token not enabled.
Version: 7.x-2.4 » 7.x-2.5-beta1
Status: Active » Fixed

This is now fixed with adjacent patch, by checking for entity_token to be enabled.
Also, a line on the project page is added.

Status: Fixed » Closed (fixed)

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