Archived topic
Background behavior changed. Does not resolve the same in browser as admin.
8 replies · Started by Jon on March 1, 2022
I have a background image that was working fine. I made a change to the page (added a container, then deleted it) that changed the way the page resolves to the user. However, in the admin side while editing the page it looks fine. The deletion of the change was to roll it back to the way it was before, but something happened behind the scenes.
Fortunately I was using a staging site, so you can see what page is supposed to look like on the live site, and you can see the odd behavior on the staging site. Moreover, since it was a staging site I can give you log-in credentials if you want to view it on the staging site.
The two sites are listed in the "private information" area below that only customer support can see.
GeneratePress 3.1.3
GPPremium 2.1.2
GenerateBlocks 1.4.2
WordPress 5.9.1
PHP 7.4.27
Hi there,
there is a BIG difference between the markup of your live site and the staging site.
The staging site has many nested container blocks which have also have links added to them. Looks like something got added or moved in the post editor that has messed it up.
Personally i would scrub the staging site, and start over with a new staging copy.
I added a container to the container that is "below the fold", the one right below the "We Stand with Ukraine" section that was added at the top. I deleted it after about 10 minutes. We weren't messing with any source code, just using the wordpress editor.
The fact that post editor can corrupt things so badly scares me for when we eventually remove the top container. Have you seen that happen much?
I have never seen the block editor break anything built with GB, it only happens if user switches to the Code view and make changes, but that generally results in an error/warning in the editor.
All am saying is that the layout you have in the Staging site is so complex and dare i say messy that trying to fix it is not something i can advise on. It would be simpler to either redo the staging or copy that section from the live site to the staging site and start over.
We did go into code view, not once.
Messy, you say. Ouch. The page used to be done with GP sections. We re-wrote the sections into blocks during the redesign using GB thinking that sections were being retired, that blocks were the future. Each section was replaced by a container. I know the support forum isn't the place to ask for tips, but if you can point me to a resource where this layout could have been done in a less messy way, I would appreciate it.
J
Please accept my apologies i did not mean to offend.
Have a look here - this is the Live Site:
https://www.screencast.com/t/cACZmaj9UwT
I highlighted the section which has the unique class of: gb-container-d82547f7 it is perfectly laid out and is built exactly as i would. This is great.
Now the staging site:
https://www.screencast.com/t/dbxmlFbig
As you can see there are lots of nested containers that all have the unique class of: gb-container-d82547f7 - so they have be duplicated and something has gone wrong.
Thats why i recommend restarting as i could not possibly explain how to correct that that layout it.
I personally would Delete that entire section.
Then edit the Live site, select that Container block, Copy and Paste into your Staging site.
Then we can assist with any changes you want to make
Thanks David. It confirms the source code got hosed somehow, even though we weren't using the code editor at all.
I'll just have to be extra careful with backups and when the time comes to modify or delete the new section.
J
Closing the ticket.
Glad to be of some help
