Closed mccrodp closed 8 years ago
If you have Token module installed you will get an improved UI for token lists!
The fallback token list can use improvement with square brackets. In addition to better documentation for suggesting site builder to install Token contrib module.
Sounds good to me, thanks! Great job in general by the way, some body of work in all of this. I'll be looking through the Access Control you have in place here when I eventually get back to Message UI! :)
Thanks! These are good UX improvements.
There is not a lot of access control as Courier is mostly an API module. The only access specific code that comes to mind is if you take advantage of the Template Collection UI. The AJAX form callback requires you to add your own hook_entity_access checking for $operation == 'templates'. RNG's rng.module and Courier System's courier_system.module implements this access check.
Oh ok...I saw the ComposeAccessCheck class and presumed this may be useful. Will take a proper look then at some stage at the above mentions.
Ah, I would avoid anything in the submodules as I dont expect them to be enabled.
What about having something like the following when you don't have the token module installed:
Also I agree to add a suggestion to install the token module.
@edurenye its a reasonable suggestion, if overwhelming. I'd prefer if site builders would just install Token module. Since site users may get confused about the purpose of many tokens.
Improved raw global token list (when token.module unavailable) and documented integration of token.module in README.
It's not entirely obvious to me what the tokens are here or how someone would use them in D8.
"Available tokens: identity, site, date, current-user"
i.e. - To use current-user, is it [current-user]?
Should this be "Available tokens: [identity], [site], [date], [current-user]"?