Closed marvinhuebner closed 7 years ago
I've found the error myself. It was no error in foundation for emails but rather in gulp-inline-css. gulp-inline-css has issues with parsing this line of code:
<a href="{{{{raw}}}}{{store url="customer/account/"}}{{{{/raw}}}}">Login</a>
If i replace the double quotes with single quotes it will work:
<a href="{{{{raw}}}}{{store url='customer/account/'}}{{{{/raw}}}}">Login</a>
But it would be a cool solution if it could be possible that the content inside the raw helper will not be attached through something else.
how fix it ?
if i want render code: {{{{raw}}}} <%=some%> {{{{/raw}}}}
Without an error messages it's hard to help you.
I've tested your example and it should work.
this happens when run build command
Currently we are building e-mail templates for magento. Magento will pass customer names etc. with variables in the template. The variables look like this
{{var store.getFrontendName()}}
. For getting the brackets into the template we need to use the{{{{raw}}}}
helper. To get the inline-css we need to runnpm run build
and get this error.How can we reproduce this bug?
Add something like this to your Inky template:
and run
npm run build
. Then the errors comes.What did you expect to happen?
Parsing the template to something like:
What happened instead?
Console Error:
Thanks in advance, Marvin