It would be nice if we could use real Tokens for the CSS path (if defining a custom stylesheet) so that if anyone needs to do any weird logic in the path, like a different file based on the current domain, or some other completely random idea, they could simply create a new Token or use one of the many existing tokens instead of the limited few custom tokens provided by the Wysiwyg module.

Given that the majority of Token is in core it's not going to add any extra dependencies, and the Token Tree could be added if the Token module was present.

I'd be happy to write the patch if I get some indication that the idea would be accepted in some form.

CommentFileSizeAuthor
#1 tokens-1835126-1.patch5.97 KBDeciphered
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Deciphered’s picture

Status: Active » Needs review
FileSize
5.97 KB

Decided I definitely needed the functionality, so patch made.

Original, proprietary tokens left alone, but I would probably recommend that appropriate tokens created to take there place and an upgrade path implemented.

alex.skrypnyk’s picture

Issue summary: View changes
Status: Needs review » Reviewed & tested by the community

Marking RTBC, since this has been working on production site for a year now.

Please include to 7.x-2.x-dev