Issue solved. An update for a plugin that caused the heavier template problems appeared unfortunately the same time as the Firefox display issue.

We’re now looking forward to some update to go back t Firefox soon.
Thank you!

We are having the same error since last weeks. Our templates and tagdiv Composer stopped working. Even reassigning standard templates creates the error. Some Templates for header/footer are also missing in front end and visual errors are all over the website. (Will create my own ticket but wanted to let you know, there is a global Problem)

Having the same issue and it seems it creates a lot more issues once you save something. All our templates started to throw errors and we are unable to assign any templates anymore.

The input fields go missing because of a css style (position:absolute and top:0). The same style creates visual errors in front end like tag navigations go missing. Switching browser is not a solution for front end.

Can you please look into this issue?

Would be nice to have this solution permanently, since the link is exausted.

Hi Calin,

thanks for your reply. The versions where both up to date when that happened and they are still.

None the less, I did as you recommended and sent a mail to contanct@tagdiv.com with the data you need.

Thank you!

A solution would be very useful. All shortcodes using get_the_id() or get_the_post() will fail. In my case the shortcodes work only inside the »external Shortcode« Block, which doesn’t allow line breaks and markup.
Would be great having a good way to handle this.

Thanks!

Hi,

I confirm, that the »solution«, setting a standard template as the default template, works. But that is not acceptable. In my case I want and need a custom template to be the default one and custom post types should not be affected by that. Moreover it is an error message I am not able to turn off.

Is there anything that I can do to get rid of this error, without relinquishing my custom template as the default one?

Thanks a lot!