Email template issue caused by component.content.studio-title (content)

Myko_P

If you have a case-portal access, You can file a case here.  

If you can't access this page, please email support@lithium.com about your issue on the same. They will resolve this for you.

Thanks for the advise, Parshant ,

I created a support ticket but it looks like Support team is unable to help me:

The error I see doesn't say much. It just points out that some of the context objects isn't used correctly. 

The Support is not equipped to troubleshoot custom code. 

I double checked the context objects in my code and didn't find any errors or typos. What could it be? 

Impossible to tell without seeing the code, basically you are in a very normal debugging scenario =)...welcome to dev-land! I would suggest you just revert back to a version before your changes (copy your changes into a text editor first for comparison) where it works again, then you copy in your changes step by step (probably best to copy each part with some kind of velocity expression one by one) back into the template and after each save you send yourself the template, like this you'll sooner or later find the offending code if you cannot find it from just looking at it.

Thanks luk ,

You can take a look at my code if you want - https://glitch.com/edit/#!/join/bc431a18-c790-4eee-ba16-6191d76983cc 

 I can't believe you guys are debugging email templates like this...Is there some Velocity engine template linter/debugger/validator?

Can't stop wondering why Lithium platform in 2018 is still using those dinosaurs from Apache foundation...

Myko_P regarding dinosaurs: good question indeed =), and then pop a ton of quite reduntant javascript on top with a very easily debuggable mix of jQuery, Angular and soon React (as it seems)^^...IMHO the entire application needs to split into a legacy branch with EOL in maybe 2 years, rebuild the entire thing on a clean tech-stack and move on from there, but I guess that's wishful thinking...

I'll have a look at the template and see if something jumps into my eyes, but can't promise... and no, afaik there is no linter/debugger or anything alike, but I can be wrong, not really an oldschool Java dev here...

Thank you, luk ! :smileyhappy:

I am using Sass version of Foundation for emails to avoid dealing with most of that inlining and table markup stuff you mentioned. So when I wrote: "I double checked the context objects in my code ..." I mean double checking of the source code in my Foundation for Emails project source HTML file. But "npm run build" i.e. parsing/inlining made a difference :robotlol: 

I am not 100% sure yet but it looks like Foundation for emails compiler can't parse/inline the right way double quotes inside double quotes i.e. email context objects inside HTML links.

In my case this one shall not pass parse/inline:

href="${emailUrls.getTapestryUrl("/user/myprofilepage/tab/user-preferences%3Aprivate-messenger")}"

 This one parsed/inlined fine:

href="${emailUrls.getTapestryUrl('/user/myprofilepage/tab/user-preferences%3Aprivate-messenger')}"

The question is would HTML links containing the email context objects work properly if URL-address is inside the single quotes? Or I should manually change it to double quotes after my code is compiled/minified/inlined?

Thank you!

Myko_P Probably best to try it out with single quotes, FreeMarker can usually handle that, but not sure about Velocity, my guess would be it's fine, but you never know 8), remember, dinosaur!

Thank you luk !

Freemarker and Velocity engine in 2018?

:manlol:

(and no decent emojis in 2018??)