Cannot update Invoice Email template because of a bad charset

[turner2f]

I have an emergency situation...

 

I have noticed that whenever I try to update my "Email Invoice Template", I get the following error...

Quote

Template parse error: unexpected character in filters : "&" at 4465

=======

I was able to narrow down that the "offending" line is...

{invoice.total | currency_format " USD "}

It seems the ...

"

... characterset is what is causing the issue.

I even tried using...



... as an alternative, but that did not work either.

=======

This issue prevents me from updating my template.

[turner2f]

UPDATE:

I found a PARTIAL workaround for this...

I went back into the HTML source code of the template and typed in the quotation marks ( not the HTML charsets ).

So that it looks like...

{ invoice.total | currency_format "USD" }

...inside the templates HTML source code.

===========

Here is where the issue lies :

After successfully saving the change, if I try to update the template a 2ND time, I end up with the SAME charset error.

For some odd reason the quotation marks that surround THIS line of code gets converted into a charset after the 1ST save, making it so that I have to constantly update THAT line of code before saving the template.

===========

FYI - Nowhere else within the template's HTML code do I have this issue where quotation marks are used ( whether as HTML charsets, or not ) with other lines of code or word content.

This issue is ONLY occurring with THIS line of code.

===========

Please reply on how I can resolve this issue.

[turner2f]

{invoice.date_due | date "M d, Y"}

 

Causes the same issue, so that it has to constantly be changed to ...

 

{invoice.date_due | date "M d, Y"}

 

In order to save the template.

[Tyson]

This is not a behavior I encounter with the WYSIWYG editor. However, I recall you had mentioned updating the editor in the past (e.g. as mentioned here) and I wonder if those updates led to this issue. You might want to try removing your changes temporarily and retesting this behavior in Blesta to see if you still encounter it with the default Blesta WYSIWYG.

[turner2f]

The only thing I did was create a template within the WYSIWYG.

I will test this line of code in one of the default WYSIWYG templates.