So I am not positive which Miva update I noticed this after, but when trying to View All Toekns (Tokenlist) of a given page, I am met with a compile error similar to this:
Looking into the error location, it seems to be hitting a compilation error with code like this:
Where there is an "if" statement within an HTML tag to add additional attributes, classes, checked, etc.
The initial View All Toekns error like this was on our OSEL page; I replaced the mid-HTML-tag IF with an IF/ELSE to write a full tag depending. This cleared the OSEL page of any 'errors' but this noted the same kind of compiling error on a different page.
The page I am trying to View All Tokens is a waitlist email template - not associated with OSEL, BASK, CTGY, etc. but still throws an error citing these pages. The above error for the CTGY page is a great example as this page has not changed for the longest time; it has always had this mid-HTML-tag MVT markup in it.
So did something change that Miva no longer likes this structure? Is there a different way to define HTML tag attributes using a MVT:IF without the longer IF/ELSE method? They pages work fine on their own client-side, but the View All Tokens process does not like it.
HTML Code:
{ "success": 0, "error_code": "MER-UTIL-TKNL-00021", "error_message": "JSON_Save_Template_Source_To_Temporary_File: Function miva_template_compile Failed with error At 135:105-135:109 - syntax error, unexpected IDENTIFIER, expecting \u0027\u003E\u0027 on file: ctgy.mvc" }
HTML Code:
<a href=/"&mvt:category:cf:ctgy_pdf1;/"<mvt:if expr="'.pdf' CIN l.settings:category:cf:ctgy_pdf1"> target=/"_blank/"</mvt:if>>&mvt:category:cf:ctgy_pdf1_text;</a>
The initial View All Toekns error like this was on our OSEL page; I replaced the mid-HTML-tag IF with an IF/ELSE to write a full tag depending. This cleared the OSEL page of any 'errors' but this noted the same kind of compiling error on a different page.
The page I am trying to View All Tokens is a waitlist email template - not associated with OSEL, BASK, CTGY, etc. but still throws an error citing these pages. The above error for the CTGY page is a great example as this page has not changed for the longest time; it has always had this mid-HTML-tag MVT markup in it.
So did something change that Miva no longer likes this structure? Is there a different way to define HTML tag attributes using a MVT:IF without the longer IF/ELSE method? They pages work fine on their own client-side, but the View All Tokens process does not like it.
Comment