Tokenized Email not pulling URL, Path, or Link

I'm also facing problem to generate email when a new post is created. Also I found no way how to differentiate the two tokens with same keyword, given below. If I use [url] what information will be there in the email?
[url] Absolute path alias to the referenced node.
[url] Absolute path alias to the referenced user.

Thanks in advance for any kind of help.

Can you try the dev version of the module? I think this is fixed.

I think this is a duplicate of #306324: Node tokens not working for comment actions.

Still getting the same thing. Is there any other way to get the token to pull through? The results in my tokenized e-mail are still coming back as [link], [path], and [url].

kevinsiji - Did this work for you our are you still having trouble as well?

This looks like it could be a duplicate as well. I don't believe that patch mentioned in the duplicate did any good for me.

Anyone have any new info on this one?

I'm still having the same issues. Nothing new.

Just to be absolutely clear, you're still having the problem with a recent version of token? 6.x-1.x-dev?

Hi,

I just tried upgrading to 6.x-1.x-dev to see if it would fix the problem and it definitely does not.

Email displays "[link], [url], [path]" -- no actual URLs to be found...

I'm currently using Drupal 6.11. If I select the "Send email" (non-tokenized version) the URL is included in the email as it should be.

[EDIT]
For anyone who's looking for a workaround to link to a node URL, try this -- it worked for me:
[site-url]/node/[nid]

@berkchoff - can you please clarify what action is triggering the sending of the mail?

I'm triggering "Send tokenized e-mail" from Actions, which is triggered from the Workflow module.

I have installed:
Workflow 6.x-1.1
Rules 6.x-1.0-rc2 (required for Workflow)
Token 6.x-1.x-dev (2009-May-15)
Triggerunlock 6.x-1.0

Thanks, this is helpful. I think I was imprecise in what I need.

Can you clarify what event is triggering the mail? Is it a node creation?

If you can provide a step by step set of instructions to for recreating the bug it will help a lot.

No, the email is not triggered by node creation.

Workflow is a module that allows one to create states (or stages) of publishing workflow. E.g. "Draft", "Revise", "Published", etc.
It is highly customizable and so you can trigger different actions based on moving from one workflow state to another. So, in my case, I am simply triggering the "Send tokenized email" when the workflow state changes from "Draft" to "Revise" (and vice versa --using the same action for both for testing purposes). These states can be applied to each individual node type and actions are called for each state transition for each node type.

It appears that the association between workflow state transition and action are captured in a table called trigger_assignments. Columns are hook (all values here are "workflow"), op (identifies the workflow state & node), aid (action ID), and weight. There are a few different tables associated with Workflow, but the node data is captured in a table called workflow_node whose columns are nid, sid (workflow state ID), uid and stamp.

Hopefully, this is closer to what you're looking for?

P.S. I realized that I incorrectly stated that Workflow requires the Rules module. I also have Node Expire installed, which is what requires Rules. Workflow does NOT require the Rules module.

Same problem here. +1 to follow.

you can build the url of the node with available tokens through [site-url]/node/[nid]
but how can you actually expand url alias as generated by pathauto module?

my nodes have path using the following tokens:
[termpath-raw]/[title-raw]

but the URL generated by pathauto via [title-raw] has a few filters on (separator instead of blank spaces and special characters, forced lower case, transliteration, etc)

so, using [termpath-raw]/[title-raw] tokes in actions does not give the actual node URL. is there any solution to this?
(of course some [url] token would be one, that's why i'm posting here - otherwise i'll open a new feature request)

Same exact issue here with Workflow. I was having published posts also sending a post out to twitter. The twitter post doesn't come up with any of the tokens. EXCEPT for the %site_name, which works fine.

To check, I also had the workflow send me a tokenized email as well. Same thing.

Here's my workflow

MOVE POST TO NEXT STATE
PUBLISH POST
PROMOTE POST TO FRONT PAGE
SAVE POST
POST TO TWITTER
SEND TOKENIZED EMAIL

I'm using pathauto and i made sure that the Twitter module was heavier in the DB.

Ideas?

At least I've got it narrowed down to something in token.

I have same problem with workflow-NG when sending an email on node creation of a specific (custom) content type.

When triggered emails are sent (HTML Mail is installed) Tokens are not replaced.

commentmail module does replacements and it works with HTML.

i gave up.

i put in the rules module and it works fine.