add rules integration to token module

ah perhaps I'll add some notes to the token cache clearing code it implements. It's basically ported from workflow-ng. It's necessary as rules and workflow-ng works with variables in different states, e.g. the unchanged node and the changed node on node update. To reflect this changes when token works on both nodes I need to clear the cache.
This is also the cause why I don't use token_replace_multiple() - I might have multiple variables of the same type.

ok some more on this and how rules/workflow-ng uses token:

* rules/workflow-ng allows to make use of tokens nearly everywhere - which leads to things which are quite useful, but were not intended originally for the integration. I'm referring to things like using a token together with the string comparison condition to check whether a node is published. I understand that this is no usual token use case and I don't suggest to develop token in such a direction.

But also token is used as it should be, for replacements in on site messages, mails, log messages, breadcrumbs, ...

* Token improvements I suggested were always for "valid" use cases like pre-selection and filtering of raw tokens vs safe tokens and the performance thingie.

* For other use cases rules already has a "php input evaluator" and I'll add conditions for such simple things as checking whether a node is published.

Anyway the patch isn't about any token improvements. It just empowers rules to make use of token replacements and could also go into the rules module. As rules allows other module to provide input evaluators it would make sense to put it into token though.

If you prefer to not have it in the token module, it's no problem. I 'd go and add it to the rules module then. I just suggested to add it to token, because I would say
* it's the cleaner way (rules provides the hook, token implements it)
* it's easier to deal with token API changes/improvements.

if someone wants to use it in the meanwhile:

Just download the attached file, rename it to token.rules_.inc and place it in your token module directory. Then go to the administer modules page and just hit submit - that's it.

yep, that would be great. I'm working towards the first beta release - I'd like to have this issue sorted out until the beta, so people don't have troubles getting token integration :)

yes, it should be token.rules.inc. Thanks for clarifying this.

>Is there any reason that this support can't simply be included with rules module?
No, it can be with rules.

>Are there reasons to put it into token?
Imho
* it's the cleaner way (rules provides the hook, token implements it)
* it's easier to deal with token API changes/improvements.

>Wouldn't it be more beneficial to have it in rules.module so that it can be updated and evolve along with that code?
I think it could better evolve in token - as it could evolve with improvements of token. I plan to not change the rules (input evaluator) API after the beta.

So the dependency thing isn't the problem. There is no real problem having it in rules - it'd be just like the CCK integration which was in token: It works, but it would better fit the other way.

ah, great! thanks a lot!

I've just released the beta yesterday, so it's awesome to have it committed now :)

Please don't reopen fixed issues like this, open a new one. If the problems appear only in friendlist actions, open an issue there. Else open a rules issue.