We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With cascading themes it's easy to set up different shops with one code base and several sub themes for each installation.
When putting email templates in /themes/, they're not recognised when emails are sent from the backend, e.g. Order_StatusEmail.ss
Order_StatusEmail.ss
IMHO sending emails should switch to the defined frontend theme, send the email and switch back for each email.
When email templates are in app/templates, this should still overrule themes' templates.
The text was updated successfully, but these errors were encountered:
emails should use configured themes
629a827
fixes silvershop#793
Merge pull request #799 from wernerkrauss/fix-793-794
6be2a2b
Improve email generation and testing fixes #793 fixes #794
fixed by #799
Sorry, something went wrong.
168bb8e
fixes #793
No branches or pull requests
With cascading themes it's easy to set up different shops with one code base and several sub themes for each installation.
When putting email templates in /themes/, they're not recognised when emails are sent from the backend, e.g.
Order_StatusEmail.ss
IMHO sending emails should switch to the defined frontend theme, send the email and switch back for each email.
When email templates are in app/templates, this should still overrule themes' templates.
The text was updated successfully, but these errors were encountered: