• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Clone Wordpress Site - Only Home page accessible

RodStr

Basic Pleskian
Created a staging site for one of my domains, the clone process of the Wordpress Toolkit ran through to completion without any errors.

But, I can only access the main page of my staging site.
Any of the page links do not open up their respective pages in the staging site.

Anybody run into this? Solution?

We are on Plesk 17.0.17 u51 running on Windows server 2008R2

Thanks in advance!

Rod
 
Not sure exactly WHY this fixes the issue, but it did...

I loaded up the Twenty Sixteen theme onto the staging site and Activated it.
Then went back and activated the Enfold theme the client is using.
All of a sudden all the "missing" pages appeared.

I guess we are resolved... just don't understand why.

Rod
 
It could be an issue with direct links between pages. Could you please clarify, how exactly links did not work? It means 404 errors occurred, or links from the staging follow to the original site?
 
I thought this was resolved, but just ran into the same issue today (on the same site).
Clone to staging site subdomain, home page works just fine,
any other page linked off the main menu returns a 404 page.

Cannot browse directly to those pages either.

Tried the method that worked last time of loading a different theme, activating it, then switching back and activating the old theme.
No go this time.

I can send detailed example but rather not post the actual site name(s) in a public fashion.



One thing I see as odd, is if I edit the pages I cannot get to directly through the browser (can't get to from outside the WP Admin environment)... I CAN find and edit the pages in the WP Admin. Just seems the cloned site configuration somehow cannot locate them. Making a change and updating the page, does not fix this either. Preview from inside the pages doesn't find it either.


Rod
 
Last edited:
So... did the upgrade to WP 5.1 on the staging site... now it works.
Again... I don't get it.

The production site is on 5.0.3, (which is what I cloned from).
But I had to install 5.1 for it to work on the staging site.

Rod
 
After going around and around on this issue yet again, I think I have a definitive answer.
If you clone a WP site that has its Permalinks structure set to "post name"
"something" is not properly updated in the paths in the database in the resulting clone.

Simply setting the permalinks to PLAIN (and SAVE), then returning them to "Post name" (and SAVE)
and all works just peachie.

Have torn down the clone multiple times now, and recreated it (each time the menu pages were dead)... did the above and all is well.

Hopefully the last post in this thread, and hopefully it saves someone else days of headaches.


Rod
 
Back
Top