Closed (won't fix)
Project:
Token
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
31 Jul 2007 at 00:22 UTC
Updated:
26 Mar 2010 at 00:12 UTC
Jump to comment: Most recent file
Comments
Comment #1
fagoyep, I agree that this would increase the usability of the tokens a lot. Unfortunately it won't be easy to implement...
ah and you could add workflow-ng too.. :)
Comment #2
drewish commentedfago, there's no better motivator for me than someone saying one of my ideas would be too hard to implement. so here's a patch. i'm sure the token devs will have some better ideas of how to set it up but it's a working prototype.
Comment #3
fagohm yes, but the given node is seldom available on configuration time - so this would be hard to use, or?
I would love to be able to state the used node type, for which then I get the replacements
Comment #4
gregglesI added audio to the list of modules - thanks for the tip.
About this help...I agree with fago in #3 - how often is a $node object actually available?
I think better would be to create your own module specific plain html help information...
Comment #5
fagoCould you add workflow-ng too please?
@topic: That's difficult too.. If the node type changes, the available token changes too..
Comment #6
arhak commentedI would recommend you to start splitting
theme_token_helpinto two separated theme functions like #576592: theme_token_list (split theme_token_help in two) (which is a D6 issue)then, every replacement list that might be needed can be easily themed with
theme_token_listonce the list of tokens gets filteredComment #7
dave reidComment #8
dave reidComment #9
dave reidI don't think this is worth including in the scope of the module. We don't have anything like this in D7 tokens, so I don't think it make sense to add another interface when it would be dropped in D7.