Site unreachable after php upgrade on Bluehost, help needed

[bleher]

under public_html

.htaccess
# Use PHPBETA as default
AddHandler application/x-httpd-phpbeta .php
# Set PHP handler to application/x-httpd-phpbeta on Fri Dec 18 07:18:52 MST 2015.

htaccess-php-upgrade-backup
[empty]

under public_html/SECONDARYDOMAIN

no htaccess file

under public_html/SECONDARYDOMAIN/Catalog
no htaccess file

under public_html/SECONDARYDOMAIN/Catalog/admin
the htaccess file quoted earlier

under the MAINDOMAIN
no htaccess file

[bleher]

My current php configuration is

PHP 5.6 [Beta, check site functionality for compatibility after enabling]
All files with the extension .php will be handled by the PHP 5.6 engine.
Latest version of PHP.

Also available as alternative are:

PHP 5.6 (Single php.ini) [Beta, check site functionality for compatibility after enabling]
Same as PHP 5.6, but all subdirectories will use ~/public_html/php.ini
PHP 5.6 (FastCGI) [Beta, check site functionality for compatibility after enabling]
All files with the extension .php will be handled by PHP 5.6 FastCGI processes.
FastCGI for PHP makes all your PHP applications run through mod_fastcgi instead of mod_suphp. This eliminates the overhead of loading the PHP interpreter on every hit. Since it is always in memory ready for the next hit, the responses will be generated faster.

[mc12345678]

Two things come to mind. Since the admin is accessible, but the catalog is not, perhaps there is some important difference in the includes/configure.php and admin/includes/configure.php. Could you please post each, obscure your admin directory (if it is listed in plain text) and your DB credentials (but validate for yourself that they are exactly the same between the two).

The second thought is trying FastCGI because I thought that suphp might be an issue, but I haven't done any research related to it. I recall seeing that potentially suhosin could be a problem and making a broad leap/assumption was thinking that suphp is somehow associated with suhosin... I may be wrong in that.

Last potentially related issue, MAIN_DOMAIN, how do the contents of that folder/area relate to ZC? Is that where your old ZC is/was? Or is it just a sort of "placeholder" allowing you to have a secondary/tertiary domain associated with your account?

[mc12345678]

Just had another thought/test.

If you create a file in your domain sub-directory with the following contents and then try to access it, does it work?

<?php
echo 'hello';

[bleher]

Creating a hello.php with the suggested content returns
hello
when accessed via SECONDARYDOMAIN.co.uk/hello.php

/includes/configure.php reads:

<?php
/**
* @package Configuration Settings circa 1.5.4
* @copyright Copyright 2003-2014 Zen Cart Development Team
* @copyright Portions Copyright 2003 osCommerce
* @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
* File Built by zc_install on 2016-03-10 06:28:04
*/


/*************** NOTE: This file is similar, but DIFFERENT from the "admin" version of configure.php. ***********/
/*************** The 2 files should be kept separate and not used to overwrite each other. ***********/

// 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://***.co.uk');
define('HTTPS_SERVER', 'https://***.co.uk');

// 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', '/***/');
define('DIR_WS_HTTPS_CATALOG', '/***/');

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', '/home1/***/public_html/***/***/');

//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', '/home1/***/public_html/***/***/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/');

// define our database connection
define('DB_TYPE', 'mysql');
define('DB_PREFIX', '');
define('DB_CHARSET', 'utf8');
define('DB_SERVER', 'localhost');
define('DB_SERVER_USERNAME', '***');
define('DB_SERVER_PASSWORD', '***');
define('DB_DATABASE', '***');

// The next 2 "defines" are for SQL cache support.
// For SQL_CACHE_METHOD, you can select from: none, database, or file
// If you choose "file", then you need to set the DIR_FS_SQL_CACHE to a directory where your apache
// or webserver user has write privileges (chmod 666 or 777). We recommend using the "cache" folder inside the Zen Cart folder
// ie: /path/to/your/webspace/public_html/zen/cache -- leave no trailing slash
define('SQL_CACHE_METHOD', 'none');
define('DIR_FS_SQL_CACHE', '/home1/***/public_html/***/***/cache');

// EOF

admin/includes/configure.php reads

<?php
/**
* @package Configuration Settings circa 1.5.4
* @copyright Copyright 2003-2014 Zen Cart Development Team
* @copyright Portions Copyright 2003 osCommerce
* @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
* File Built by zc_install on 2016-03-10 06:28:04
*/


/*************** NOTE: This file is similar, but DIFFERENT from the "store" version of configure.php. ***********/
/*************** The 2 files should be kept separate and not used to overwrite each other. ***********/

/**
* WE RECOMMEND THAT YOU USE SSL PROTECTION FOR YOUR ENTIRE ADMIN:
* To do that, make sure you use a "https:" URL for BOTH the HTTP_SERVER and HTTPS_SERVER entries:
*/
define('HTTP_SERVER', 'http://***.co.uk');
define('HTTPS_SERVER', 'https://***.co.uk');
define('HTTP_CATALOG_SERVER', 'http://***.co.uk');
define('HTTPS_CATALOG_SERVER', 'https://***.co.uk');

// 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');

define('DIR_WS_ADMIN', preg_replace('#^' . str_replace('-', '\-', zen_parse_url(HTTP_SERVER, '/path')) . '#', '', dirname($_SERVER['SCRIPT_NAME'])) . '/');
define('DIR_WS_CATALOG', '/***/');
define('DIR_WS_HTTPS_ADMIN', preg_replace('#^' . str_replace('-', '\-', zen_parse_url(HTTPS_SERVER, '/path')) . '#', '', dirname($_SERVER['SCRIPT_NAME'])) . '/');
define('DIR_WS_HTTPS_CATALOG', '/***/');

// 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_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', preg_replace('#.includes$#', '', 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', '/home1/***/public_html/***/***/');

//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', '/home1/***/public_html/***/***/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/');

// define our database connection
define('DB_TYPE', 'mysql');
define('DB_PREFIX', '');
define('DB_CHARSET', 'utf8');
define('DB_SERVER', 'localhost');
define('DB_SERVER_USERNAME', '***');
define('DB_SERVER_PASSWORD', '***');
define('DB_DATABASE', '***');

// The next 2 "defines" are for SQL cache support.
// For SQL_CACHE_METHOD, you can select from: none, database, or file
// If you choose "file", then you need to set the DIR_FS_SQL_CACHE to a directory where your apache
// or webserver user has write privileges (chmod 666 or 777). We recommend using the "cache" folder inside the Zen Cart folder
// ie: /path/to/your/webspace/public_html/zen/cache -- leave no trailing slash
define('SQL_CACHE_METHOD', 'none');
define('DIR_FS_SQL_CACHE', '/home1/***/public_html/***/***/cache');


// Define the webserver and path parameters
// Main webserver: eg-http://www.your_domain.com -
// HTTP_SERVER is your Main webserver: eg-http://www.your_domain.com
// HTTPS_SERVER is your Secure webserver: eg-https://www.your_domain.com
// HTTP_CATALOG_SERVER is your Main webserver: eg-http://www.your_domain.com
// HTTPS_CATALOG_SERVER is your Secure webserver: eg-https://www.your_domain.com
/*
* URLs for your site will be built via:
* HTTP_SERVER plus DIR_WS_ADMIN or
* HTTPS_SERVER plus DIR_WS_HTTPS_ADMIN or
* HTTP_SERVER plus DIR_WS_CATALOG or
* HTTPS_SERVER plus DIR_WS_HTTPS_CATALOG
* ...depending on your system configuration settings
*/
// EOF

All paths are correct as far as I can tell

As for server directory structure, I have several domain names all hosted on the same server, i.e.
MAINDOMAIN directory is accessed via MAINDOMAIN.com and points to public_html
SECONDARYDOMAIN directory is accessed via SECONDARYDOMAIN.co.uk and points to subfolder SECONDARYDOMAIN under public_html
This subfolder in turn contains a folder CATALOG (which contained the old 1.3.8 version of ZC and which I have since removed) and a folder CATALOG2 which contains the new 1.5.4 version of ZC
TERTIARY DOMAIN directory is accessed via TERTIARYDOMAIN.com and points to subfolder TERTIARYDOMAIN public_html

I'll try switching to FastCGI but wait until you have been able to check the configure.php files
Thanks.

[mc12345678]

Well, unfortunately because of the "security" actions taken there is no useful information in the above post to provide support. **** in one file looks like **** in the other... So from your side, you'd have to do the one for one comparison. I would almost suggest using a comparison tool to line up the lines equivalent in both files to see if/what the differences are. Since the sample php file worked, and your admin works, there is something about the catalog that doesn't... The first place to start is with the configure.php files. Then to look at/for the logs directory. Try to force an error to be generated and verify that it happens. I usually use a malformed sql search after including application_top in a file in the root of the admin folder (after login, try the file, check the logs directory). So permissions on the folder could be a problem or something else after all that.

[bleher]

The *** represented the folder names etc. and I verified that they are identical and correct in each case, so unless there is something else strikingly wrong with the configure.php files I suppose they aren't the problem?