Layouts blank after update

Support
#1

Unfortunately my site is messed up. I tried to fix it but now after 4 h I decided to renew the support license to ask you for help.

my site was affected by an autoupdate to WP 6.2. I followed the advise to remove the themefolder to install the latest version of pro.

Unfortunately afte upgrade of pro to the newest version, I found that the single layouts went corrupt somehow. They showed up but aren’t editable, nor are they rendering as expected on the frontside.

I then downgraded Wordpress to 6.1.1 and tried to revert to a previews backup (march 18th) on my server (plug-ins, theme 5.1.5 pro, uploads, database)

But whatever I do, the problem still is there. Also header and footer are showing up wrong.
I really fear I need to rebuild the whole page, but that’s really really frightening. I really hope you can help here.

P.s i flushed cache and also I finally turned off wp autoupdates

#2

Hello @flogee,

Thanks for writing in! Can you please clone your site to a staging site so we can proceed with the troubleshooting? It is also best to use the March 18 backup for the staging site so that we can figure out why the layout becomes blank and at least recover those layouts.

If you haven’t created a staging site, please check this out:

Kindly let us know how it goes.

#3

Hi,

I have cloned the site here for you to look into, you can uns the same user-credentials: https://v8qg4zvfpqm.c.updraftclone.com/

thanks for your help!

#4

Hello There,

We cannot log in using the given credentials.

  • see the secure note below.

Thanks.

#5

:see_no_evil:Sorry, I turned off the plugin that asked for login verification. It should work now to login with the given credentials to the cloned site. Thanks for looking into it again​:pray:

#6

Hi, I turned off login-Security plugin, it should be possible for you to login now to the cloned site. Thanks!

#7

I know it’s not your fault and you are probably busy, but my site is already down for days now and it makes me very nervous :weary:, I would really appreciate you help, thanks!

Also what puzzles me is how to take care that this doesn’t happen again in future situations where an update is needed. Where do layout templates get stored? In database in files? Thanks!

#8

I tried to roll back to a full server backup from December 2022 ( not the cloned site that I cloned for you), the problems are the same, missing layouts and problems with menus and headers etc. I don’t understand. How can this happen? Where does the data for layouts etc of cornerstone get saved and how can it get lost?

#9

It seems like more and more people show up in the forum with similar problems. Please let me know if i can count on your help. Or if I need to rebuild everything (maybe with another theme). I can’t have the site broken for such a long time. Thanks

#10

Layout data is in the database. When you roll back you should roll back the database as well so it sets it self up for Pro5. I can try to help if that’s not an option with a SQL update.

You can check if your in this inbetween state. If you see cs_layout_archive and not cs_layout that means you’ve got Pro 6 data.

Let me know if this helps.

#11

Hi Charlie, i am very happy you are here to help me, i am desperate to get my site back.

Unfortunately i seem to have had a problem with my regular backups connection to my storage space so i dont have recent versions of the database. :exploding_head: i just realized, my backups did not have the database included, so i was only able to revert the files but not the database.

I created a staging-site that i cloned a few days before as @ruenel has advised me to do.
And i reverted the actual site to a state of 6th of December 2022, that unfortunately does show the exact same problem about the layouts missing.

Now i just followed your advice and checked both databases for “cs_layout_archive” or “cs_layout”.
on the actual site and as well on the staging-site’s DBs both i get the same results: i can not find any content by the string “cs_layout_archive”, but i found “cs_layout” within the tables *_options and *_posts.

on both sites i have (reverted and) activated PRO Version: 5.1.5 now. and both are not rendering the layouts and styles properly anymore. all caching tuned off and cleared style cache.

Yes I would really need your help to retrieve the layouts, and ideally to also get it working with PRO V6.

#13

Okay if you reverted and you see cs_layout then you really you should be fine that’s what Pro5 is expecting. Maybe turning on WP_DEBUG can give us some answers. What is the post_status of one of these cs_layout posts? Should be in *_posts. Your headers look like they are working right? Do you see JSON in the post_content of one of these cs_layout posts?

I’d probably start by turning off the caching plugins if you haven’t already. See if one of those plugins turned off helps.

#15

cs_header and cs_footer seems to be affected also, i see “Create a Menu” and “Assign a menu” at places where i had working menus already set.

in the post_content is see this: “_modules”:[]}]}]}]}]}]}]}]},
seems as it has too many brackets. maybe corrupted while updating?

#16

I just found a working backup of the database from dec 22, the site looks good! I am so glad! Thanks for pointing me to the database!

…now i just need your advise how can i take care that the same problem doesnt happen when i update to V6? thanks!

#17

Hey awesome to hear you are good.

Did this layout issue happen when you went into Pro6 or from the revert? Did you have any issues going from 5 to 6 or have we not tried this yet? I’d always recommend trying the latest on a staging first. And if you are fine there you should be fine on your production. From the JSON you posted it looks like the HTML got unescaped causing parsing issues. What exactly were the steps you took to get to this point?
Have a great day

#18

Thanks this time it worked! I did first update to pro-v6 and then update to Wordpress 6.2.

#19

You are most welcome @flogee.

#20

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