Templates and templateparts empty

Bugs
1

Fist of all thank you very much for all new improvements and features - you are doing such a fantastic job! The new themer now loads all the templates everytime without the whitescreen issue, that sometimes happend before.

There is just a little new issue:
I have a simular problem with the new template previews like @sunny Template previews don't show in Firefox but also in chrome (tested with the latest chrome and firefox developer browser).
Furthermore, on my side there is an empty template message on all templates (all of them are cwicly made templates with content):

parts Cwicly Themer
parts Cwicly Themer1535×921 23.3 KB

templates Cwicly Themer
templates Cwicly Themer1500×946 21.3 KB

I’m using the latest cwicly & WP version on php 8.0

Thanks for your help! :slight_smile:
Greetings
Marc

2

Hi @msteinlein,

Sorry to hear you’re experiencing trouble with this.

Rest assured, the error with the templates not displaying properly in Firefox will be addressed in the next update, so please bear with us.

As for your templates displaying empty on chrome, this is unusual as I cannot reproduce this issue on my end.

Could you possibly let me know what plugins you have actvivated on your installation?
Thank you in advance.

3

Hello @msteinlein,

Just checking this out.
Is this still happening on your side?

Thanks in advance.

4

@Louis, with the latest Cwicly version, this is happening for us on a site with WPML installed.

We have an almost identical site without WPML installed that seems to work fine, so that combined with the error itself will hopefully give you a starting point:

api-fetch.min.js?ver…4dabf8bf2c7adf21a:2 
 GET https://xyz.com/wp-json/cwicly/v1/render?_locale=user 500
j	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
h	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
P	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
a	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
P.method.r	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
a	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
t	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
g	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
A	@	api-fetch.min.js?ver…4dabf8bf2c7adf21a:2
(anonymous)	@	index.js?ver=1.2.9.9.5:171
Ur	@	react-dom.min.js?ver=18.2.0:10
El	@	react-dom.min.js?ver=18.2.0:10
(anonymous)	@	react-dom.min.js?ver=18.2.0:10
v	@	react.min.js?ver=18.2.0:10
ce	@	react.min.js?ver=18.2.0:10

Let me know if you need any more information.

5

@Louis & @Araminta, just confirming this issue is still present with 1.3.0.1.