I would like to know the answer too. Anyone here know what is the answer to that question. I'll do some research and get back to you if I discover an anything. You should email the people at iPage as they probably could assist you..
Actually absolute paths are generally used in the serverside langauge. I hardly ever see anybody use absolute paths for images. most general webmasters use relative and leave absolute to the back end (serverside)..
Actually on regular html you should use the relative or the url and leave the absolute paths to the serverside languages...
I have over 200 pages and I prefer using relative paths. Most of my stuff is in a general layout though... pages in one directory, images in one directory, examples in one directory, and so forth... so if I need to access a specific file, I know where to look already..
There are a few paths that are absolute, just because, but I would say about 98% are relative..
I think I mainly went this route too because most of my coding is done offline and it helps when it comes to previewing offline. I can essentially have a mirror of my iPage site available to me without being online...
So what about client-side scripting references - absolute or relative?.
Define an array? (example please!).
I use absolute. There is good reason for me to use it. Lets say I call an image from my root to my image dir.... something like /images/pic.jpg think of how many times that would change if I wrote the page differently, or implimented a new directory structure and placed the page in a new directory 2 levels down. None. Not once..
Also, I use includes on almost every page... and quite often use the same include in ALL directories... and call scripts and pictures in those includes. I can't use ../../../ because it would only work in one instance..
Using absolute linking takes no extra time, and is a better solution for the long run, no matter if your using client/ server or both...