Header-Editor: "Invalid template markup"

After working with headers for several weeks withoud problems, I now get the following message in the header-editor:

“Invalid template markup. This could be due to changes introduced by a third party plugin. The front end of your site should still function normally”

Indeed, the frontend is OK, but it’s not easy to work with the header while this message is shown.

The only plugin that has been added is EnviraGallery, wich I also use in other problems without any effect on the headers.

I read the other posts relating to this error, but could not find a solution. I don’t use any HTML-Code in the header, that could cause the error …

I’ll send you Backend Access via SecureNote.

Best regards

Uli

Hi Uli,

I got this error in the console log:

This JS file is not fully loaded in the header builder:

https://2019.grk-hr.de/wp-content/themes/pro/cornerstone/assets/dist-app/js/cs-vendor.js?ver=3.5.4

This issue is very similar to this: https://theme.co/apex/forum/t/pro-editor-wont-load/29841/12?u=thai

Please follow this ticket above.

Let us know how it goes!

Hi thai,
thank you for your help. According to the issue you posted, I changed the memory limits and execution time in php.ini and wp-config.php. But the error is still shown in the editor. If I look at the concole, I see a “Template parse error Error”:
Template parse error Error: [object Object] at cs.js?ver=3.5.4:2040 at p (cs.js?ver=3.5.4:2044) at cs.js?ver=3.5.4:2053 at RegExp.[Symbol.replace] (<anonymous>) at String.replace (<anonymous>) at m (cs.js?ver=3.5.4:2053) at Array.map (<anonymous>) at h (cs.js?ver=3.5.4:2066) at e.default (cs.js?ver=3.5.4:2030) at cs.js?ver=3.5.4:2401 {"e":{},"template":"\n\n<a data-cs-observeable-id={{_id}} data-cs-observeable={{observer}} class=\"e{{_id}} x-anchor x-anchor-toggle {{data.class}} x-hide-lg x-hide-xl\" tabindex=\"0\" data-x-toggle=\"1\" data-x-toggleable=\"e{{_id}}\" data-x-toggle-hash={{data.toggle_hash}} >\n\n \n <span class=\"x-anchor-content\">\n \n<span class=\"x-graphic\" aria-hidden=\"true\" >\n\n \n<span class=\"x-toggle x-toggle-burger x-graphic-toggle\" aria-hidden=\"true\" >\n\n \n <span class=\"x-toggle-burger-bun-t\" data-x-toggle-anim=\"x-bun-t-1\"></span>\n <span class=\"x-toggle-burger-patty\" data-x-toggle-anim=\"x-patty-1\"></span>\n <span class=\"x-toggle-burger-bun-b\" data-x-toggle-anim=\"x-bun-b-1\"></span>\n\n \n</span>\n</span> </span>\n\n \n</a>\n{{portal name=\"x_before_site_end\" ....

Any other idea? The setup of my server did not change the last weeks and till yesterday I could work perfectly in the header builder of this site …

Cheers
Uli

Hi Uli,

It was the Navigation Layered Element that is causing the issue. It seems that the data is corrupted. Please delete and add it back again.

Thanks

Hi paul,
I can confirm that it’s related to the Navigation Layered Element. If I delete it, everything works fine.
Now I added the Element again, saved without changing any settings, still works.
Then did all the changes (mainly font, colour, menu). As long as I don’t leave the editor, everythings still fine. After saving and reload, the error is back.
So it seems to be a problem with one of the settings in the element.
Any idea?
Uli

I did delete and add it once again, with a lot of save and reloads after every single change I did - now it seems to work, although still all settings are the same.
I now try to do this with all the other headers and hope, they will work to …

Best regards

Uli

Hi Uli,

Try to monitor your changes and see what change is causing the error. Try saving after each change in the settings so that you can pin point what settings triggers the error.

Thanks

Hi Paul, that’s what I already did (see post above). Everything works fine now, but I have no Idea, what caused the problem.

Let’s hope it stays stable now …

Best regards, have a nice weekend!

Uli

Have a nice weekend too, Uli.
If you need anything else we can help you with, don’t hesitate to open another thread.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.