Main
Index 		Search
Posts 		Who's
Online 		Log
In

Home: Discontinued/Classic Products: Listings Manager (Realty Manager & Auto Manager):
Paths queery on server change

 
 


willydoit
User

Jun 17, 2009, 10:48 PM

Post #1 of 3 (4189 views)
Shortcut
Paths queery on server change Can't Post
Hi,

I am in the middle of moving a number of accounts to a new server and during the installation of listings manager I have noticed that the listings and homepage paths appear to need to be different to the images paths in order to work.

The server is linux and the cgi-bin is outside the public area which is public_html, I have placed the listings path as ../../../public_html/walkers/listings and this seems to work, if I remove the public_html part of the path the listings editor doesnt show that any images are uploaded for the item, put it back and they are there, however in order to get the listing editor design images to appear I have to use the path ../../../walkers/images/login_auto.jpg without the public_html element otherwise the images dont show. Is this normal and why do two paths to basically the same location need two different formats to work?

I should point out that at present we havent changed the nameservers over and are installing and accessing via a temp access facility via the ip address so it may be that some elements are actually being picked up from the old website if a part uses the http://domainname path to reach any items.

I have a number of installs to transfer this weekend so would feel a lot happier knowing that everything will work with these settings as I dont want lots of angry phonecalls come monday morning and have the pressure of sorting them all out at once.

Clarification would be appreciated.

Thanks in advance


Donna
Staff / Moderator


Jun 19, 2009, 11:35 AM

Post #2 of 3 (4187 views)
Shortcut
Re: [willydoit] Paths queery on server change [In reply to] Can't Post
Hi there,

The difference between the two paths is that one is a server (file) path, and one is a web path. These are actually two different things.

The server path is the actual location on the server. The web path is the path relative to your document root -- which is the public_html folder, and corresponds to www.yoursite.com. The filepath can go "outside" of that path. When cgi-bin directories are outside of the public_html (it's a common method of setting up CGI) the file path needs to go "below" the public_html directory. A web path can only go as far as the document root, so it can never go below the public_html. In the web path, the cgi-bin appears to be within the document root, although it's not really.

This might be a little confusing, but in the long run: Yes, that's normal. :)

For image paths, though, I'd actually recommend skipping the relative paths (aka, the ../../../ part). Instead, start the path with a slash (which takes you back to the document root) and enter the directories from there, which will work from any directory. So, instead of:

../../../walkers/images/filename.jpg

...try this:

/walkers/images/filename.jpg

This is good practice for your templates, as well.

I hope this helps. :)

Donna

--
support@interactivetools.com


willydoit
User

Jun 22, 2009, 12:15 AM

Post #3 of 3 (4163 views)
Shortcut
Re: [Donna] Paths queery on server change [In reply to] Can't Post
Thanks Donna,

All makes sense now.