Blank page when trying to access www.website.com/catalog or www.website.com/catalog/admin

[liongate]

I've been trying to find the source of this problem for some time. I have copied all of the osc files to the catalog folder of my root. However, when I attempt to access the catalog through either http://www.website.com/catalog or http://www.website.com/catalog/admin all I get is a blank page. First I thought it was because I didn't have a php.ini file, but I am told by my host that the php.ini is at the server level rather than the site level and I do not have access to it. It should be noted that the site worked fine when I installed oscommerce above the root through the Application Vault provided by my host. The problem is that I want to install in the website root/catalog folder for the sake of permitting me to update it with the rest of the site when I do an update. Here are both of my configuration files:

 

//catalog/admin/configure.php:

 

define('HTTP_SERVER', 'http://www.website.com');// eg, http://localhost - should not be empty for productive servers

define('HTTPS_SERVER', 'https://www.website.com');// eg, http://localhost - should not be empty for productive servers

define('ENABLE_SSL', true);// secure webserver for checkout procedure?

define('HTTP_COOKIE_DOMAIN', 'www.website.com');

define('HTTPS_COOKIE_DOMAIN', 'www.website.com');

define('HTTP_COOKIE_PATH', '/catalog/');//This should be the same as your DIR_WS_HTTP_CATALOG.

define('HTTPS_COOKIE_PATH', '/catalog/');//And this should be the same as your DIR_WS_HTTPS_CATALOG.

 

define('DIR_WS_HTTP_CATALOG', '/catalog/');//This is your catalog directory - where osc is on your server. By default, this should be /catalog/ - if you have it in a catalog file.

 

define('DIR_WS_HTTPS_CATALOG', '/catalog/');//I don't think very many people actually have a separate directory for the secure part of their website, so just leave this the same as the above, unless you do have a separate directory.

 

//Just leave these be, unless you've been changing things around. These are defining the subfolders of oscommerce. If you want to add some folders, like, for example, a subfolder for videos on your website, here's where you put it. If you want to rename some of your subfolders, here's where you change it so that osc knows the new names.

define('DIR_WS_IMAGES', 'http://www.website.com/images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');

define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');

define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

 

define('DIR_WS_DOWNLOAD_PUBLIC', 'pub/');

define('DIR_FS_CATALOG', 'E:\\CustomerData\\webspaces\\webspace_00100629\\wwwroot/catalog/');

define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');

define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

 

 

//includes/configure.php:

 

define('HTTP_SERVER', 'http://www.website.com');// Guess what! This is the same as http_server on includes/configure.php. Amazing. Note, however, if you want your admin area to be secured under your ssl certificate, which you probably do, this should be what you have under https_server in your file above.

 

define('HTTP_CATALOG_SERVER', 'http://www.website.com/catalog');// This is the link to your catalog. If you have your shop in the root of your website, it'll be the same as the above. If not, it'll be something along the lines of http://www.widgetsofdoom.com/catalog.

 

define('HTTPS_CATALOG_SERVER', 'https://www.website.com/catalog');

 

define('ENABLE_SSL_CATALOG', true);// Set to true if you want ssl to be enabled when linking to the catalog from the admin, false if you don't.

//

//Same as above, except it is the root folder, rather than the catalog folder. Even if your site's in the catalog folder, this goes to the admin.

 

define('DIR_FS_DOCUMENT_ROOT', 'E:\\CustomerData\\webspaces\\webspace_00100629\\wwwroot/catalog/');

 

define('DIR_WS_ADMIN', '/catalog/admin/'); //Your admin directory, the url version. If your store is a subfolder in your root (i.e. it's in a folder called catalog), then it would probably be /catalog/admin/. If you want to change your admin location to deter hackers, here is one of the two places you change it.

 

define('DIR_FS_ADMIN', 'E:\\CustomerData\\webspaces\\webspace_00100629\\wwwroot/catalog/admin/');// This is much the same as the document_root, except you add on the catalog folder, if needed, and the admin folder. This is the other place you change admin location.

 

 

define('DIR_WS_CATALOG', '/catalog/');

define('DIR_FS_CATALOG', 'E:\\CustomerData\\webspaces\\webspace_00100629\\wwwroot/catalog/');// Much the same as the two above it, except pointing to the catalog folder, or the folder containing oscommerce.

 

define('DIR_WS_IMAGES', 'http://www.website.com/images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_CATALOG_IMAGES', DIR_WS_IMAGES);

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');

define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');

define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

define('DIR_WS_CATALOG_LANGUAGES', DIR_WS_CATALOG . 'includes/languages/');

define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');

define('DIR_FS_CATALOG_IMAGES', 'E:\\CustomerData\\webspaces\\webspace_00100629\\wwwroot/images/');

define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');

define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');// Just defining all the subfolders. If for some reason you're integrating some more subfolders into osc admin section, here's where you define them. Otherwise, just leave them alone.

[liongate]

Okay -- I figured this one out on my own. What I was trying to do was to move an existing installation from a folder that existed above the root level into a folder beneath the root. The original installation was created by an installer program provided by my host server. The problem is that many of the the oscommerce php files had their source code modified by the installer program in ways that made the files not portable. A clean install of a new catalog folder with the insertion of correct config files resolved the issues.