multisites errors after moving site to new hosting 6 Years, 3 Months ago
|
Karma: 0
|
Just moved an account to a new hosting service.
The main site has multisites installed.
Unable to create the symbolic link [includes] -> [/home4/xxx/public_html/includes].
Unable to create the symbolic link [libraries] -> [/home4/xxx/public_html/libraries].
Unable to create the symbolic link [Joomla_3.5.1-Stable-Full_Package.zip] -> [/home4/xxx/public_html/Joomla_3.5.1-Stable-Full_Package.zip].
Unable to create the symbolic link [htaccess.txt] -> [/home4/xxx/public_html/htaccess.txt].
Any ideas?
|
|
|
|
|
Re: multisites errors after moving site to new hosting 6 Years, 3 Months ago
|
Karma: 54
|
The reason is simple.
If you used our backup shell script or did a "tar" to make a zip of the code then you have the absolute path of the directories where the master was located.
When you restore the code into another directory, JMS warns you when the path is different than the one expected.
So, if you have changed of location you have to delete the existing symbolic link and let JMS rebuild new links to the new "master" location.
When you are on your linux account, you can use the "ls -l" command to see the list of files and directories with the current link.
The link is probably the one of the "old server" that must be replaced by a new link for the new server.
|
|
|
|
|
Re: multisites errors after moving site to new hosting 6 Years, 3 Months ago
|
Karma: 0
|
I used akeeba backup to move the site
|
|
|
|
|
Re: multisites errors after moving site to new hosting 6 Years, 3 Months ago
|
Karma: 0
|
can you please be more specific on what I need to do.
it's a shitty blue host account.
ssh is difficult at best with their stupid keys system.
|
|
|
|
|
Re: multisites errors after moving site to new hosting 6 Years, 3 Months ago
|
Karma: 0
|
from which directory? ls -l lists nothing
|
|
|
|
|
Re: multisites errors after moving site to new hosting 6 Years, 3 Months ago
|
Karma: 54
|
You have to check in the "deploy directory".
The place where the slave site is deployed (See JMS Manage => (4) Website directory).
This will give you the path where is deployed the slave site.
Once you are in this directory, check the list of symbolic link.
in SSH, you can use the command : ls -l
You can also use an FTP tool to see the list of files and directories but some tools does NOT show you if this is a link or a physical file or dir.
Once you have identified all the symbolic links, you have to delete them.
When deleted, you can Open/Re-save the slave site definition to rebuild the missing links.
|
|
|
Last Edit: 2018/08/22 09:03 By edwin2win.
|
|
|