Upgraded to 1.5.4........now my admin page doesn't open

[lrfowler]

UPGRADED TO 1.5.4........NOW MY ADMIN PAGE DOESN'T OPEN..
what happened?
I tried all the suggestions in the forum....
what am I missing?

I knew I shouldn't have tried rushing thru this update at 9PM at night...
thanks.

[lrfowler]

here's my admin/includes/configure.php
<?php
/**
* @package Configuration Settings circa 1.3.9
* @copyright Copyright 2003-2010 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 2010-10-27 08:41:40
*/


/*************** 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. ***********/

// 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
*
* If you desire your *entire* admin to be SSL-protected, make sure you use a "https:" URL for all 4 of the following:
*/
define('HTTP_SERVER', 'http://www.cavalryfiberglass.com');
define('HTTPS_SERVER', 'https://www.cavalryfiberglass.com');
define('HTTP_CATALOG_SERVER', 'http://www.cavalryfiberglass.com');
define('HTTPS_CATALOG_SERVER', 'https://www.cavalryfiberglass.com');

// Use secure webserver for catalog module and/or admin areas?
define('ENABLE_SSL_CATALOG', 'false');
define('ENABLE_SSL_ADMIN', '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_ADMIN', '/store/larry_admin/');
define('DIR_WS_CATALOG', '/store/');
define('DIR_WS_HTTPS_ADMIN', '/store/larry_admin/');
define('DIR_WS_HTTPS_CATALOG', '/store/');

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)
//the following path is a COMPLETE path to your Zen Cart files. eg: /var/www/vhost/accountname/public_html/store/
define('DIR_FS_ADMIN', '/home2/cavalry1/public_html/store/larry_admin/');
define('DIR_FS_CATALOG', '/home2/cavalry1/public_html/store/');

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', 'znc_');
define('DB_SERVER', 'localhost');
define('DB_SERVER_USERNAME', 'cavalry1_znc1');
define('DB_SERVER_PASSWORD', '');
define('DB_DATABASE', 'cavalry1_2');
define('USE_PCONNECT', 'false');
define('STORE_SESSIONS', 'db');
// for STORE_SESSIONS, use 'db' for best support, or '' for file-based storage

// 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', '/home2/cavalry1/public_html/store/cache');

// EOF

[mc12345678]

Besides changing your secret admin path now that it has been publicly posted, I would suggest at least temporarily creating a new setof configure.php files through the following process, and modifying as necessary to apply to your store. The current configure.php files use a lot more autolocation and simplified assignments to constants.. I didn't exactly see a formatting issue with the above configure.php, but I didn't compare to a "live" one and also don't have the store side to compare with as there may be other differences notyet considered.

See: http://www.zen-cart.com/entry.php?3-...d-of-upgrading

Also, when say applied the patches of the forum, are you referring to: http://www.zen-cart.com/showthread.p...s)-with-v1-5-4

What php version are/were you using?

[lat9]

Is there anything in your /logs folder? When you say that your admin "doesn't open", I'm assuming that you're being presented with a whitescreen.

[DrByte]

The recovery suggestions posted by others are good places to start.

I knew I shouldn't have tried rushing thru this update at 9PM at night...

There's nothing to rush about an upgrade if you're following the published upgrade procedure of staging the upgrade in a test COPY of your site to work out all possible kinks before applying the upgrade to the live site.
If you're looking for a way to simplify the process slightly, see: http://www.zen-cart.com/entry.php?3-...d-of-upgrading for guidance on keeping the live site going with only a couple minutes downtime when fully ready to go-live with the tested upgrade.

[lrfowler]

yes a white page.....possibly my configure.php I brought over from my backup file is corrupted in some way?
-----------
here's a log file (myDEBUG-adm-1422040421-466077.log)

[23-Jan-2015 12:13:41] PHP Parse error: syntax error, unexpected T_STATIC in /home2/cavalry1/public_html/store/larry_admin/includes/classes/class.admin.zcObserverLogEventListener.php on line 118

can you interpret?

---------------
Jan 23 2015 11:59 -- database_upgrade
NOTE: Skipped upgrade statements:

1 - See details at bottom of page for your inspection. - (Details also logged in the "upgrade_exceptions" table.) - Note: In most cases,

these failed statements can be ignored, - as they are indications that certain settings may have already been set on your site. - If all

the suggested upgrade steps have been completed (no recommendations left), - you may proceed to Skip Upgrades and continue configuring your site.

[lat9]

yes a white page.....possibly my configure.php I brought over from my backup file is corrupted in some way?
-----------
here's a log file (myDEBUG-adm-1422040421-466077.log)

[23-Jan-2015 12:13:41] PHP Parse error: syntax error, unexpected T_STATIC in /home2/cavalry1/public_html/store/larry_admin/includes/classes/class.admin.zcObserverLogEventListener.php on line 118

can you interpret?

That log, which exposes your secret admin directory name to the world, is a by-product of attempting to run your Zen Cart v1.5.4 on oldy-moldy PHP 5.2.17.

You should upgrade your version of PHP (Zen Cart v1.5.4 has been tested/validated with PHP versions up to 5.6) or apply the patch that DrByte described here: http://www.zen-cart.com/showthread.p...33#post1268233

[mc12345678]

**deleted by poster as same content as previous post**

[lrfowler]

yes upgrading to PHP 5.4 fixed it..
thanks