[wp-trac] [WordPress Trac] #59056: LOST Formatting/Settings when Live Site is copied to Staging or Cloned
WordPress Trac
noreply at wordpress.org
Sat Aug 12 23:47:21 UTC 2023
#59056: LOST Formatting/Settings when Live Site is copied to Staging or Cloned
--------------------------+------------------------------
Reporter: lhe2012 | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Formatting | Version: 6.3
Severity: normal | Resolution:
Keywords: | Focuses:
--------------------------+------------------------------
Comment (by lhe2012):
Hi Neko Jonez -or- Whoever is receiving this,
== My Response to Your Questions
Comment:
In your ticket you say without any plugins running... Yet in your
environment there are three...
**==>**Yes, in the environment I generated the base ticket info from,
3 plugins.
**==>**I have tested a number of scenarios, all result in the same
issue.
**==>**Issue being, Once copied to Staging ... Format/Settings are
Lost.
**==>**To re-create issue ... Issue Exists, Even when NO Plugins are
installed.
Also, is the live site and local/staging site the exact same in terms of
settings? Same database, same php version and such?
**==>**I Believe so, but I don't know exactly the process that takes
place ...
**==>**On SiteGround Hosting, I just Reference LIVE Site, then click
on "Create New Staging Copy"...
**==>**Then a Staging sub-domain is automatically created, such as
"stagingXXX.original-LIVE-URL"
**==>**Then LIVE Site is Copied (in some way) to Staging URL
"stagingXXX.original-LIVE-URL"
How do you run that staging site?
**==>**To run, I just click on the automatically created URL,
"stagingXXX.original-LIVE-URL"
These pieces of information would help to debug this issue.
**==>**Big UPDATE On This (2 Notes) ...
**==>**(1) SiteGround was able to develop a fix & has installed it
across ALL of there servers.
**==>**(1) SiteGround correspondence is below.
**==>**(2) This condition still exist on WPEngine LOCAL Environment
Application
**==>**(2) Issue exist with Literally NO Plugins, just wordpress 6.3
Install ... then Clone Site
**==>**(2) So, Using LOCAL to Clone the Site, ends up with SAME Issue!
-------------------------------------------------------------------------------------------------
== Current Status
So I don't know where original issue is being derived from WordPress 6.3
-or- outside applications.
○ **Both SiteGround Hosting & LOCAL** (local WordPress environment)
**resulted in same issue.**
○ **SiteGround** has **either a Fixed -or- developed a WorkAround** (See
correspondence below)
○ **LOCAL** **still has the problem**.
○ But the condition I suspect (not sure), is due to 6.3.
○ I **saw this issue in RC2, RC3 & Production versions** of WordPress
Thank You Very Much,
Larry
== Some SiteGround Correspondence follows ...
-------------------------------------------
Aug 11, 2023 05:01 PM (**Me to SiteGround**)
-------------------------------------------
Hi SiteGround People,
QUESTION: Did you guys fix the Staging issue? Staging is working Normal
now again for me!
I just did a bunch of tests, and results are good each time.
Even the Live sites (I had problems with before), are working now.
○ The original Staging Copy is still there with the problem.
○ When I create a New Staging Copy of the Live site, that New Staging Copy
is good!
○ I made NO Changes to the Live site, but when I re-stage, it works now!
So QUESTIONS: Did you find something? Did you change something? What was
it?
I am very interested, because I was able to re-create the problem with
“WPEngine’s LOCAL” environment.
When I use LOCAL
1. Create bare minimum 6.3 site
2. Install NO Plugins
3. View Site (Everything is Good So Far)
4. Clone Site in LOCAL Environment
5. View Site (Formatting/Settings have been LOST)
I just tested the above LOCAL process again, and problem is still there in
LOCAL … But things work with SiteGround Staging!
Thank you very much,
Larry
-------------------------------------------
Aug 11, 2023 11:03 PM (**SiteGround to Me**)
-------------------------------------------
Hello Larry,
I am glad to inform you that our **team found a fix for the reported
problem** and **already deployed it on all of our servers**. The
**solution** essentially **deletes the following transient record
"wp_core_block_css_files" from the *_options table**. Regrettably, I am
not able to provide more detailed information on the matter.
Thank you for your cooperation!
The ticket will now be marked as closed and if you need any other
assistance you can request such from here or use the Help Center.
Best Regards,
SiteGround
Senior Technical Support
== END of My Response
--
Ticket URL: <https://core.trac.wordpress.org/ticket/59056#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list