Kinsta cache prevents layouts from being assigned correctly

Hi there,

I’m still dealing with this issue:

Especially translated layouts can’t be assigned correctly.
How did you solve it with the caching? I’m consistently clearing Kinstas cache but still no luck.

I have created 3 layouts for 3 woocommerce product categorie archives and assigned them accordingly.
It all worked fine for the base language (German) but for the English translation it’s pure gambling.

Hey @ArtOfSpring,

My colleague mentioned clearing the cache but it’s actually not linked to the issue. He just needed to clear cache always to see the result of his test.

He didn’t actually fix the issue per se. He said or his solution was to duplicate the Kimono Dress layout because it’s corrupted. If that solution is acceptable to you, you should now work with the copy. It’s named Kimono Dress (bck).

We are currently clueless as to why those layouts are in German when they should be in English and why some English templates are not loading. Please ask your web host to give you the error log then post the error log in the secure note then give us FTP access also so we could try some troubleshooting procedures.

Thanks.

Hi,

thanks for getting back to me.
The copy solution isn’t a solution for me anymore as I created new layouts and assigned them.

We are currently clueless as to why those layouts are in German when they should be in English and why some English templates are not loading.

Also the layout preview for 2 English product category layouts is showing a 404 page when you select a product category page for preview (but it shows if the shop is selected in preview).

The one exception is https://test.lemanja.de/en/pro/layouts/1286. Here everything is working fine.

Please find the error log in the secure note.

Hi @ArtOfSpring,

Thank you for the credentials, Is there any way to completely deactivate the Kinsta cache for a while?

And can you try running Transient Cleaner to clear all transient cache?

Let us know how it goes,
Cheers!

Kinsta cache is deactivated now.

As for the transient cleaner I received a wordpress warning to deactivate the plugin because it’s functionality is already part of WordPress core since 4.9

Just wanted to let you know, in case it wasn’t your doing already, that it is all working fine now. Disabling the cache might have done the trick. But still this is a huge issue for later changes on a live environment with necessary caching.

Glad to hear that it’s working now, @ArtOfSpring. Just monitor what you perform on your site and processes done by your web host and 3rd party plugins so we’ll have an idea what exactly caused the issue.

Thanks.

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