• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Cloning - wordpress _posts table

RodStr

Basic Pleskian
Server operating system version
Windows Server 2019
Plesk version and microupdate number
Plesk Obsidian v18.0.57_build20231205.06 os_Windows 2012/2016/2019/2022
We've been using Plesk for quite awhile now and the WP Toolkit regularly.
What we have been doing is using the CLONE site feature to "roll out" our dev site to our production site.
From time to time we will clone in the other direction to give the dev site a "clean starting point".

Today while looking for something else in the _posts table for one of our Editors, I ran across something odd.
The _posts table in our dev site has entries in the guid field for all 3 of our various sites prototype, dev and our production site.

So, question is... isn't the WP Toolkit supposed to replace the database on the destination of a clone.
From what we are seeing it isn't really a merge operation either.
If I look at the _posts table of the 3 sites, the counts in the guid field are entirely different across the 3 databases.

We are having SEVERE speed issues on all 3 of those sites, and trying to track down possible causes.
Seeing that the "production" site has guid entries for the "dev" site, I can see that causing problems potentially.

Counts based on contents of "guid" field of _posts table

PRODUCTION DATABASE
575 entries for https Production site URL
1066 entries for https Dev site URL
115 entries for https Prototype site URL
0 entries for http Production site URL
156 entries for http Dev site URL
0 entries for http Prototype site URL

DEV DATABASE
473 entries for https Production site URL
255 entries for https Dev site URL
2319 entries for https Prototype site URL
0 entries for http Production site URL
156 entries for http Dev site URL
0 entries for http Prototype site URL

PROTOTYPE DATABASE
280 entries for https Production site URL
211 entries for https Dev site URL
2498 entries for https Prototype site URL
0 entries for http Production site URL
156 entries for http Dev site URL
0 entries for http Prototype site URL

I thought "maybe" revisions??? So installed the typical Optimize Database after blah blah blah... ran it with a 0 setting for revisions and the counts didn't change at all.

Just doesn't seem right that I should have addresses from dev and proto in production and vice versa.

Any thoughts ?
 
As a test, I just now cloned our production site to a new location, and then cloned it over the top of the dev site.
The record counts were identical for the two clone to destinations.
Still has records for all 3 sites in _posts, but it shows consistency and that the clone DID overwrite the database properly.
Now I'm really lost as to why the DB has multiple sites listed in it.
 
GUID means unique identifier and usually values of this column are not changed. So if you use sync data or any another tool to partially copy data, GUIDs stays unchanged and any posts that created on dev env still have GUIDs that mention dev url.
 
Back
Top