You are not logged in.
Pages: 1
Hi,
I’ve moving a site to another server and have done the usual stuff – editing the config file correctly.
But I am still getting the $path_to_site: from the previous server.
Do I have to edit the path anywhere else apart from the config file?
cheers.
Lawrence
Offline
Hi,
I’ve changed these, yes.
I’ve also searched the database and found no reference to the old host.
This is odd.
Offline
The site is here: http://101.128.5.8/~nyary60 (but it doesn’t work given some issues with the htaccess), hosted on Site5.
TXP admin works, though, and I get this in the preflight check:
$path_to_site: /nfs/c02/h11/mnt/18830/domains/nyary604.com.au/html
Which is the path define on the live site, hosted on MediaTemple (www.nyary604.com.au)
Thanks!
Offline
Add the domain with the Site5 IP address to your hosts file so you can test it on your machine locally and see what the path is then – it should act as though the site is live on the new server
If you haven’t used hosts before, heres a few “how tos” on mac, pc and a full resource
Offline
Hi tye,
Thanks for your help.
Where would I find this hosts file?
I had a look at all TXP files and nothing seems to match.
Offline
It’s not a Textpattern related file. See the links Tye provided.
Anyways, path_to_site is updated and generated automatically when the frontend of the site is accessed. The path doesn’t need to be set anywhere, it’s dynamic. Given your issues with .htaccess and inability to access the site’s frontend, the path will still point to the old location until you access the frontend.
Last edited by Gocom (2012-05-08 23:35:27)
Rah-plugins | What? I’m a little confused… again :-) <txp:is_god />
Offline
What’s your htaccess issue?
I’ve used Site5 and had zero issues with multiple Textpattern installs.
Offline
Thanks and sorry for not reading tye’s post in full – the links explain it all very well.
And thanks Gocom for your explanation too.
MattD, In the end the htaccess issue was resolved. Site5’s original suggesion involved BASHing (whetever that is) and updating the php.ini file, but all it took was a tweak of the htaccess file.
Offline
Pages: 1