Uh oh! App.preview-error.missing-zone.cs_layout

[brianv3]

I am creating this new thread to leave a secure note with my login credentials.

Hi, I’m experiencing the same issues as @Kev and @Vinvu. Uh oh! App.preview-error.missing-zone.cs_layout. Sometimes it seems to work. I’ve tried all the common troubleshooting steps. I can provide logins to a staging server for your review.

This issue is present in 6.5R1 and the final 6.5 release. I put the staging server login in the secure note.

Thank you.

[prakash_s]

Hello @brianv3,

Thanks for sharing the login details I went ahead and checked your settings it seems might be the issue of cache. I just purge all the cache from the Speed Optimizer and it is working fine on my end. I have tested it on the Google Chrome browser version 126.0.6478.127. I would also suggest you please clear your browse cache and recheck it or check out in the private mode of the browser.

Thanks

[brianv3]

Hi @prakash. You missed the error and it is not the cache. We cleared any caches from the server level though the theme clear the cache. To make sure we did multiple installs. The screen shots you sent me of the site does not show the error. I see that @doncomarketng has the same error now. The main blog doesn’t seem to have issues. It is CPT related pages. I am getting the same messages under the same circumstances @doncomarketing and like me I don’t think he’s stuck on a caching issue when it is a theme issue. I need this fixed. Thank you.

[DoncoMarketing]

@brianv3 – Was able to workaround the error by simply selecting something else from the preview pane and setting it back to my desired CPT but per my forum entry as well – this needed to be done every time the builder loaded an archive.

Also, separate but could be related for some reading this in the future – be sure you have archives enabled on the CPT.

[brianv3]

Hi @DoncoMarketing, Thanks for your input. I appreciate it. I have been able to work around it sporadically by doing as you indicated. I previously created several CPTs, and they are working fine on the front end so far. However, despite clearing caches (I leave them off during development), I clear them anyway and am constantly refreshing the browser. I think if you duplicate a CPT as a template for another CPT despite taking the appropriate steps, as I did with the ones that are working on the front the CPT is getting corrupted somehow. Perhaps if there is more than one CPT or archive window open at the same time, they get cross-linked somehow. So if I’m working on an archive and switch to a different open archive to compare info, maybe it gets corrupted then, even though I set it back to the correct preview settings, refresh the browser and clear the cache.

[marc_a]

Hey @DoncoMarketing,

Thanks for sharing your tips and we really appreciate your time and effort.

@brianv3 hope it helps.

Cheers!

[brianv3]

Hi @marc_a, I am still having the same issue, and I just want to confirm that the development team is reviewing it and working on a solution so I can work on the site. I’’ leave the staging site active for you. I appreciate Themeco’s attention to this matter. Great job on the new version 6.5!
Thank you.

[charlie]

I’ll setup some text for that localization at the very least on Monday. And I’ll take a look at the issue where the layout isn’t being shown in the preview as well. Thanks for sending this our way and the kind words. Have a great weekend.

[iOBAdmin]

Thanks for sharing @DoncoMarketing

I was experiencing the same issue - the solution for me was the enabling of “Archive” for the CPT.

[Rough_Works_Consulting]

Any update on this would be great. Its breaking for all my archive layouts.

[marc_a]

@Rough_Works_Consulting,

Our developer will get in touch on this thread about his findings. Please stay tuned.

Thank you.

[charlie]

Pro 6.5.1 will try to force the Preview to work properly and will also give you a better error message. From the sites I’ve seen you can get this error from not having a “Posts Page” setup in the WordPress setting. On WPML there are some issues with the preview viewing the wrong translation

Or not having your Custom Post type have an archive setup. (This is in ACF)

In WPML if you are previewing a post that is not in the correct translation it can happen. In the preview manager here you can change the post to one with the correct translation. We’re going to try to setup something where it will auto redirect to the correct translation, but is proving to be challenging.

Let us know if this helps