• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

PMM - Migration Manager - from /home/httpd to /var/www Frontpage ext.

B

BoXie

Guest
Hi,

When using Plesk Migration Manager for transferring websites from the same (7.5.4 up-to-date) Plesk version BUT with different webroot paths (/home/httpd to /var/www), websites with Frontpage Extensions installed get broken. All the .htaccess files and some FP ext. files still contain the old path's (/home/httpd).
I found this out after a lot of searching and thinking .. so a little workaround / fix or user notification would be nice !

For the rest : Migration Manager is a great tool for ehm .. migrations !! It worked really well over here .. and saved me a lot of time ! Well done SW-Soft !

(Migrated from FC2 / 7.5.4 to Centos 4.2 / 7.5.4)
With regards,

Sander van Boxtel.
 
Hi,

Just insert a symbolic link to the new path.

In shell run:

ln -s /var/www /home/httpd

That fixed it for me.

Greetings,
Bart
 
Indeed ... that is a smart solution ..

But i still think that the move from /home/httpd/ to /var/www should contain some documentation for admins. Like for instance , what kind of troubles they are likely to run-in to.

Also .. will that symbolic link also work for PHP scripts with 'absolute path' entries in their config files ? I guess the open_basedir restriction will block it ?
 
Hi,

I red here in the forum some suggestion to keep the /home/httpd/vhosts (move the /var/www/vhosts) dir and change the path in /etc/psa/psa.conf to:

HTTPD_VHOSTS_D /home/httpd/vhosts

But that didn't change my httpd include, neither after restarting apache or psa, so I deceide to do it by symlinking.

Yes some php scripts like mambo could break, you will have to change the config.php in each mambo dir (3 lines I guess). On my server only a few broke (where several additional modules where installed).

Then, I wanted to change to /var/www because on next update/migration you will have the same issues again, so better now than later...

Greetings
Bart
 
Originally posted by bartje3
Yes some php scripts like mambo could break, you will have to change the config.php in each mambo dir (3 lines I guess). On my server only a few broke (where several additional modules where installed).
Did your PHP scripts break even with the symlink in place from /home/httpd/vhosts to /var/www/vhosts?

If so, can you list the scripts that broke?

That list would be very useful!

Thanks.
 
Haven't tried it ...

PHP scripts almost always have only one or two 'path' variables to set in a config file. I just modified those vars.
 
Back
Top