I create a new template and set it to new email.
I create a new email and then any text that was set as bold is not applied.
I check the template again but it’s still bold in the template.
I create a new template and set it to new email.
I create a new email and then any text that was set as bold is not applied.
I check the template again but it’s still bold in the template.
Hi Kyle, what version of eM Client are you currently using?
Can you make a screenshot of the issue?
Thank you,
Paul.
Thank you for getting back to me - here is a screen shot of the version.
I checked for a new update and there was a prompt stating there was no update available.
Additionally, I have done a video of the bug:
http://www.solidfiles.com/d/c3b288084e/emclient-template-bold-bug.mp4
Hi Kyle, thank you for reporting this, this issue has been reported and we’ll be working on a fix for future releases, sorry for any inconvenience caused.
Also, the issue only occurs when the bold formatting is inserted on the first line of the template.
If for example bold formatting is on the second line, the whole template should be ok.
Thank you and again, sorry for the inconvenience,
Paul.
Thanks for the reply!
Unfortunately the work around did not work for me.
I added
[BLANK LINE]
as the first line of the template as text (in white font), but the second line:
v1.xx available
was still not bold on creating a new template.
I’m glad it’s already logged as a bug - it’s actually not an issue for me - I just wanted to ensure it was known about!
I’ll continue to reapply my bold version details in my emails until fixed!
Kind regards,
Kyle.
Hi Kyle, yes this sounds as this would not work either, as the problem is the Bold text can’t currently be the first text in the Template.
I was actually notified the issue has already been fixed and the fix will be merged into a future update, however note it might not be the first one you’ll be prompted to update to as several currently internal updates have already been released in the meantime.
Thank you for understanding and thank you for reporting the issue,
Paul.