Suddenly Front end blank. Admin fine.

[lat9]

Since you say that the admin is working, I'd focus on the differences (especially in the DIR_FS_CATALOG definition) between the files /YOUR_ADMIN/includes/configure.php and /includes/configure.php.

If you could post the contents of those files (minus the database configuration items) within the "Code" tags (i.e. the # in the menu-bar when you're writing your post), perhaps one of us can see the difference that's causing your whitescreen issue.

[mc12345678]

I've got a huge list of the same stuff I can see on the admin side of the site when I click the info page. PHP version and all the tables that I can get if I go to "version" in the admin of the site.

It's quite a large list. Should I paste it here somewhere?

I would say not necessary at the moment. Result does identify a few things though. 1) php is loading at the catalog level, 2) loading of the site when using the url to include the foldername is loading. In addition to lat9's suggestion of providing the configure.php files (though if I remember correctly the last time I applied the constant she referenced to a site with a poorly written configure.php file at least some results were obtained, not nothing), providing the .htaccess file at the root of the domain with any reference to the admin directory obscured (admin) may be of benefit, though another test that could be performed is attempting to goto yoursite/the_php_info_file.php and see that you get redirected to the sub-folder and the phpinfo file from above. (may require regenerating the file if it was removed as suggested).

[Nepherael]

Since you say that the admin is working, I'd focus on the differences (especially in the DIR_FS_CATALOG definition) between the files /YOUR_ADMIN/includes/configure.php and /includes/configure.php.

If you could post the contents of those files (minus the database configuration items) within the "Code" tags (i.e. the # in the menu-bar when you're writing your post), perhaps one of us can see the difference that's causing your whitescreen issue.

Here we go. Also, there are no transactions on this website. It is used as a catalag. I checked the php info and it says there are no "additional modules" installed either. I've been looking through these configure files but I haven't been able to find any issues.

The site is contained in the directory "new" on the server. Godaddy does not allow subdirectory installs of the primary domain on the account so it required redirects from the root to point to the subdirectory. Everything still points to where it is supposed to.

Admin/includes/configure.php

  define('HTTP_SERVER', 'http://lightsforholidays.com');
  define('HTTPS_SERVER', 'https://lightsforholidays.com');
  define('HTTP_CATALOG_SERVER', 'http://lightsforholidays.com');
  define('HTTPS_CATALOG_SERVER', 'https://lightsforholidays.com');

  // secure webserver for admin?  Valid choices are 'true' or 'false' (including quotes).
  define('ENABLE_SSL_ADMIN', 'false');

  // secure webserver for storefront?  Valid choices are 'true' or 'false' (including quotes).
  define('ENABLE_SSL_CATALOG', 'false');

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
  // these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
  $t1 = parse_url(HTTP_SERVER);$p1 = $t1['path'];$t2 = parse_url(HTTPS_SERVER);$p2 = $t2['path'];

  define('DIR_WS_ADMIN', preg_replace('#^' . str_replace('-', '\-', $p1) . '#', '', dirname($_SERVER['SCRIPT_NAME'])) . '/');
  define('DIR_WS_CATALOG', '/new/');
  define('DIR_WS_HTTPS_ADMIN', preg_replace('#^' . str_replace('-', '\-', $p2) . '#', '', dirname($_SERVER['SCRIPT_NAME'])) . '/');
  define('DIR_WS_HTTPS_CATALOG', '/new/');

  define('DIR_WS_IMAGES', 'images/');
  define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
  define('DIR_WS_CATALOG_IMAGES', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'images/');
  define('DIR_WS_CATALOG_TEMPLATE', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/templates/');
  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', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/languages/');

// * DIR_FS_* = Filesystem directories (local/physical)
  define('DIR_FS_ADMIN', realpath(dirname(__FILE__) . '/../') . '/');
  //the following path is a COMPLETE path to your Zen Cart files. eg: /var/www/vhost/accountname/public_html/store/
  define('DIR_FS_CATALOG', '/home/content/l/i/g/lights4holiday/html/new/');

  //the following path is a COMPLETE path to the /logs/ folder  eg: /var/www/vhost/accountname/public_html/store/logs ... and no trailing slash
  define('DIR_FS_LOGS', '/home/content/l/i/g/lights4holiday/html/new/logs');

  define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');
  define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');
  define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');
  define('DIR_FS_CATALOG_TEMPLATES', DIR_FS_CATALOG . 'includes/templates/');
  define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');
  define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email/');
  define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');

and the includes/configure.php

// Define the webserver and path parameters
  // HTTP_SERVER is your Main webserver: eg-http://www.your_domain.com
  // HTTPS_SERVER is your Secure webserver: eg-https://www.your_domain.com
  define('HTTP_SERVER', 'http://lightsforholidays.com');
  define('HTTPS_SERVER', 'https://lightsforholidays.com');

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

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
  // these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
  define('DIR_WS_CATALOG', '/new/');
  define('DIR_WS_HTTPS_CATALOG', '/new/');

  define('DIR_WS_IMAGES', 'images/');
  define('DIR_WS_INCLUDES', 'includes/');
  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', DIR_WS_CATALOG . 'pub/');
  define('DIR_WS_TEMPLATES', DIR_WS_INCLUDES . 'templates/');

  define('DIR_WS_PHPBB', '/');

// * DIR_FS_* = Filesystem directories (local/physical)
  //the following path is a COMPLETE path to your Zen Cart files. eg: /var/www/vhost/accountname/public_html/store/
  define('DIR_FS_CATALOG', '/home/content/l/i/g/lights4holiday/html/new/');

  //the following path is a COMPLETE path to the /logs/ folder  eg: /var/www/vhost/accountname/public_html/store/logs ... and no trailing slash
  define('DIR_FS_LOGS', '/home/content/l/i/g/lights4holiday/html/new/logs');

  define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
  define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');
  define('DIR_WS_UPLOADS', DIR_WS_IMAGES . 'uploads/');
  define('DIR_FS_UPLOADS', DIR_FS_CATALOG . DIR_WS_UPLOADS);
  define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email/');

[lat9]

I see no differences in the "key" definitions for those files, so that's not it.

Do you have a .htaccess file in your store's root, i.e. /home/content/l/i/g/lights4holiday/html/new/.htaccess? If so, would you post that file's contents?

[Nepherael]

I see no differences in the "key" definitions for those files, so that's not it.

Do you have a .htaccess file in your store's root, i.e. /home/content/l/i/g/lights4holiday/html/new/.htaccess? If so, would you post that file's contents?

Sure thing.

# -FrontPage-
IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*
<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName www.lightsforholidays.com
AuthUserFile /var/chroot/home/content/l/i/g/lights4holiday/html/_vti_pvt/service.pwd
AuthGroupFile /var/chroot/home/content/l/i/g/lights4holiday/html/_vti_pvt/service.grp

[lat9]

I'm not familiar with that AuthName control, but I'll note that it's referencing www.lightsforholidays.com while your configure files are using lightsforholidays.com (without the www.).

[mc12345678]

What about at: /home/content/l/i/g/lights4holiday/html/.htaccess?
(one folder up from the new directory.)

[Nepherael]

What about at: /home/content/l/i/g/lights4holiday/html/.htaccess?
(one folder up from the new directory.)

Apologies. What is there is what I pulled from the root. The new directory does not have an htaccess.

[mc12345678]

Another "direction" is related to having a local directory and contents within it./home/content/l/i/g/lights4holiday/html/new/includes/local. Is it present? What files are present? is there a configure.php file?

[RodG]

Sure thing.

# -FrontPage-
IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*
<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName www.lightsforholidays.com
AuthUserFile /var/chroot/home/content/l/i/g/lights4holiday/html/_vti_pvt/service.pwd
AuthGroupFile /var/chroot/home/content/l/i/g/lights4holiday/html/_vti_pvt/service.grp

I'd be strongly tempted to delete/rename this file. With your current zen install it doesnt appear to be doing anything, and if the domain names did match (www vs no www) it looks like it will be asking for a password to access the site, and if the auth paths are wrong, or the auth files are unreadable you could possibly end up with the blank screen. ... just a thought.

Cheers
RodG