Closed kapso closed 5 years ago
@kapso Those are related to MJML changes. See their release notes: https://github.com/mjmlio/mjml/releases
Thats interesting. What I am curious is my code has now completely stopped working, even after I rolled back to MJML v4.1.1. It started breaking after 4.1.1 => 4.2.1 upgrade, so I rolled back, but no luck. Do you think this still a MJML lib issue?
@kapso I couldn't get my MJML lib back to an older version once I'd upgraded, so I had to run with it. See #39.
Do you still have an <mj-container>
in your mjml? The change to >= 4.2.1 forced removal of that from memory.
No I am not using any <mj-container>
Closing this issue, you are right no way to rollback the MJML version. I will work on fixing the MJML syntax issues. Thanks for the quick responses and your work on this gem 👍
I am getting these errors, even though the MJML docs don't mention any of these restrictions. These errors started showing up after I upgraded JS library
4.1.1
=>4.2.1
Versions:
Errors:
mjml-rails (4.2.4)