The Token module needs to be integrated so that a skeleton can be created, but have various tokens applied at run time. Users should be able to insert the base tokens provided by Token in the node and global context. As well, users should be able to specify additional tokens which appear as fields to fill in during the creation of a Skeleton instance.
The use case in this instance is where users need to be able to specify items such as a dealer name, location, or links to other nodes (such as a location node).
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 344133_token_integration.patch | 21.28 KB | deviantintegral |
| #2 | 344133_token_integration.patch | 21.65 KB | deviantintegral |
Comments
Comment #1
agentrickardAwesome idea.
Comment #2
deviantintegral commentedHere is a patch which does the following:
This should add quite a bit of flexibility to templates, allowing one outline to be easily customized. Also, Token is now a module requirement as there is a required database table.
Comment #3
deviantintegral commentedHere is an updated patch which applies cleanly against head. I changes how the description of custom tokens is check_plain'ed, instead storing the unescaped version in the database. It also renames 'All tokens' to 'Node tokens'.
Comment #4
deviantintegral commentedCommitted to HEAD.