Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow use of CiviCRM tokens instead of Smarty variables #17

Open
jensschuppe opened this issue Feb 24, 2022 · 2 comments
Open

Allow use of CiviCRM tokens instead of Smarty variables #17

jensschuppe opened this issue Feb 24, 2022 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@jensschuppe
Copy link
Contributor

Currently, only contact tokens are explicitly supported in templates used for sending with this extension, but with a deprecated method CRM_Utils_Token::replaceContactTokens(). No other tokens are supported which makes it hard to extend on the functionality.

This extension should implement token replacement using CiviCRM's Token framework and deprecate the Smarty variables it is currently defining as placeholders.

@jensschuppe jensschuppe added the enhancement New feature or request label Feb 24, 2022
@jensschuppe jensschuppe added this to the 2.0 milestone Feb 24, 2022
@bjendres
Copy link
Member

Makes sense. What is the minimum CiviCRM version for that?

@jensschuppe
Copy link
Contributor Author

I think 4.7 - if we're not planning to provide our own tokens using some new stuff in Core, then it would be 5.44. Not sure about those special variables for multi-value fields of events (sessions, speakers, etc.) and special formats - maybe they can be handled with default custom field tokens.

Anyway, version 2.0 of the extension should not not move forward because of supporting legacy stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants