Hello @janreidelde,
that shouldn’t happen of course. When you test those emails, do you see the tag that has not been replaced?
Michael
Right, I see just the tag and it is not replaced by the actual date.
Hello,
I just saw you are referring to service emails, those tags won’t work with that kind of messages.
Michael
Well, I use it in both service emails as well as newsletters.
It work in the past e.g. in the double-opt-in email where I put in the timestamp of subscription to document when the subscription attempt happened.
I also use it in a newsletter template in the copyright section to get the year.
I assume, these are the common cases for the application of this tag and that it is used by many users. But when you say that this isn’t supported anymore, I must go down another road and implement it with a shortcode myself.
Hello @janreidelde,
you’re right, those are really common use cases and while we focused on regular newsletters, those should be working in transactional messages as well. We’ll add this to our development roadmap and we’ll be sure to add this (or fix it) in the near future. We really thank you for your precious feedback.
Michael
