Proposal: Scheduled Reminders should not (by default) use Smarty on new installs
When token rendering is enabled, and the TokenProcessor
context says to use Smarty, the TokenRow rendering barfs on any curly brace that isn't a token or Smarty. Which includes, for instance, inline CSS.
At the time that SE post was made, Smarty stripped out the CSS. It no longer does, and instead generates large numbers of errors. Rather than fight that battle, I'm curious whether Smarty on scheduled reminders is necessary and serves a purpose in a post-5.43 TokenProcessor world.
If we decided that Scheduled Reminder TokenProcessors had Smarty set to false this problem would go away.
Does anyone use Smarty here? Should they?