I would like to know the answer too. Anyone here know what is the right answer. I'll do some poking around and get back to you if I got an good answer. You should email the people at iPage as they probably can answer it..
I will be running a iPage site in conjunction with the shop and a forum so the /shop/ is necessary..
And the /includes/functions/compatibility.php is also there and has the 755 and correct owner...
Ok after some more playing around I've found that the original error goes away if I use the complete file path to all the php files mentioned in the application.php, but then more errors are found when it loads the next file :s.
So how could I fix the problem of the install files not seeing the relative paths?.
Unless you're already using a folder called 'catalog' why have you added the '/shop' subfolder?.
If you add a link on your root to the /catalog/index.php front page and return all the relative paths back to the original parameters it.
Until something else goes wrong..
Thanks for the reply..
I'm just using /shop instead of /catalog, it's not another folder inside catalog. I could also make shop.mydomain.co.za and place the files in the root there if you think it will help..
But when you mention adding a link to the index.php how exactly would I do that? sorry but I'm a complete noob..
This will add a link to an image so clicking on the image dircts the customer to where you want them to go:.
<A href="http://www.your domain/shop/page or file.co.nz"><IMG src="http://www.your online image storage/folder/file.(jpg, JPG, gif, etc)" border=0></A>.
Alternatively you could add the link to some text:.
<A href="http://www.your domain/shop/page or file.co.nz"><FONT color=#ff0000>add text here</FONT> </A>..
But my problem right at the beginning of the install. when I browse to www.mydomain.co.za/shop/install I get the errors that I posted and after playing around I found that if I used the absolute path then those errors go away, but I wouldnt want to have to edit every file in the install..
So is there a way or setting that I'm missing to get the files to use their relative paths rather?.
There may be an option under 'globals' in your iPage website provider's access portal to make such.
Changes by altering absolute paths into relative paths - I don't know enough about the subject to say for certain..
Otherwise you will probably have to move everything (with the original paths intact) from /shop to /catalog or even /root..
If you go down the latter.
Your shop's Front Page should show up without any links required (I think)...
Hi there guys and girls,.
I'm trying to set up a oscommerce demo here at work and I've run into a bit of a problem..
I've copied the catalog files to my own directory under /var/www/html/mydomain/shop/ and changed the permissions as required, but when I try and access the install page in my browser I get a blank page :s.
After a look at my logs I found this:.
[Wed Nov 05 14:55:30 2008] [error] [client 188.8.131.52] PHP Warning: require(includes/functions/compatibility.php) [<a href='function.require'>function.require</a>]: failed to open stream: No such file or directory in /var/www/html/mydomain/shop/install/includes/application.php on line 16.
[Wed Nov 05 14:55:30 2008] [error] [client 184.108.40.206] PHP Fatal error: require() [<a href='function.require'>function.require</a>]: Failed opening required 'includes/functions/compatibility.php' (include_path='/var/www/html/sit/includes') in /var/www/html/mydomain/shop/install/includes/application.php on line 16.
I confirmed that ../shop/install/includes/application.php does in fact exist..
I've tried changing the permissions for the entire folder, recopying the files and starting from scratch and searching this forum but havent found any help.
I'm using the latest version from the downloads section and php5..
If you need any other info please let me know because any help would really be appreciated..
Did you see if includes/functions/compatibility.php was there?.
Also, is this shop going to be running in conjunction with another iPage website in the root of the site? If not, you should install it in the root folder...