• 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.

Suggestion for Transfer and Migration wizard improvement

TomBoB

Silver Pleskian
Hi,

had to transfer two complete servers. Source ones both CentOS 6.7 latest updates, Plesk 12.0.18 MU#67.
Destination ones CentOS 7.1 latest updates, Plesk 12.0.18 MU#67

I came across the following:
Normal websites came across fine.
Wordpress sites with Wordpress installed in the domains root dir came across fine.
Wordpress sites with Wordpress installed in a (non-standard) subdirectory did *not* work however. When visiting the site, the browser shows error "The page isn't redirecting properly".

Upon closer inspection it became clear that the wizard hadn't copied the full config of Wordpress its setup across [ Source side:
1) Settings - General - WordPress Address (URL): http://xyz.com/subdir
2) Settings - General - Site Address (URL): http://xyz.com
]
but had re-created the Wordpress site using standard settings
[ Destination side:
1) Settings - General - WordPress Address (URL): http://xyz.com/subdir
2) Settings - General - Site Address (URL): http://xyz.com/subdir
]

Re-did the few steps to have a Wordpress site installed in a sub directory but showing as root
[see https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory and "Using a pre-existing subdirectory install" subsection] and everything's running fine again :)

Although it's more Wordpress related than Plesk, it would be nice to have this special case covered/included in the Transfer and Migration wizard.

Thanks,
Tom
 
Actually it has been already done. I've tested it on Plesk 12.5.30.
It was an issue on old APS packages, which may overwrite wp-config settings. It seems it's fixed now.
 
Awesome, thanks Dmitry!

Am a "late adopter", still running 12.0.18 MU#67 - traditionally update our servers to the latest Plesk version (12.5 in this case) only after it's really stable, plus quite a few month. To minimize chances of running into "teething problems" :) [they hold many clients business critical sites]

Thanks for feedback!
 
Back
Top