Upgraded from 1.3.8 to 1.5.1. Getting old admin screen, but version says 1.5.1

[rayw1679]

Updated 3 of 4 stores; first 2 went okay. Third was on MYSQL 4.0 and host (1and1) will not allow creation of 4.0 databases, and I couldn't convert it to 5.0 (var-something errors), so I ran zc_install on the current database. It stopped a few times, telling me to refresh the screen, and then everything appeared okay. The database now says 5.0 and the store looks okay.

After a few days, I discovered the settings for "superuser" on the other sites, and went into the 3rd one to update the other user, but the admin screen has the "old" format. Tools>Admin Settings results in a "404." Version says 1.5.1. The "Admin Access Management" tab does not display.

[DrByte]

Sounds like files are not all upgraded.
http://www.zen-cart.com/wiki/index.p...Obscure_Issues

[rayw1679]

Thank you. I ran WinMerge, and it kicked out a lot of files. However, checking a few, Winmerge defined the difference as one having an "LF" instead of "CR." The text was identical. So, if there was a bad file, it was impossible to find -- there were hundreds listed.

I FTP'd the entire admin section from the original files, and ALL my options went away.

Should I try a clean install but use the same configure files so I'm using the same database? Or, should I set-up a new store and try to copy the database? (The old backup is from SQL 4.0). I'm very confused and will appreciate your sage advice.

[DrByte]

I hope you made a backup before you blasted a bunch of different files onto the server.

I believe there's an option in WinMerge to ignore line-endings. That would help you remove those issues from the list of results.
As for it showing you problems with hundreds of files ... if the files you had on the server were the wrong ones, then hundreds of diffs wouldn't be unsurprising.

[rayw1679]

Or, could I copy one of my stores that is working fine and just replace the configs with the ones from the store that isn't working?

[rayw1679]

I copied one of my newer 1.3.9 stores (always SQL 5.0, if that matters) to a new subdirectory in the one that won't work (ohsopersonal dot com), then copied the images and configure files from the old store. Admin came up with the new sign-on, made me change my password, and then displayed an admin screen with NONE of the normal drop-down options whatsoever.

[rayw1679]

Thank you, DrByte, for post # 4. Somehow, I missed it until now, apparently since I posted twice shortly after you did. However, you were exactly correct (as usual). I also set WinMerge to show only differences, which made it easier to read.

On my previous attempt, it appeared Fizezilla didn’t copy all the files. (I did the copy and then overlay on the server, instead of on my PC, and I suspect it timed out or something.) My WinMerge problem was I hadn’t set the option to ignore carriage return differences. However, it was also reporting files different that when I clicked to view, it said it was identical. Strange.

I started over. I created a SQL 5.0 database, and restored it from 1.3.8a’s 4.0 database (my working store). I set-up a demo site of 1.3.8a with the new 5.0 database, and it worked fine. I switched it to the regular store and it is running fine today, although I have to upgrade promptly to 1.5.1 because our host is switching to PHP 5.4.

I then copied the 1.3.8a store to another demo folder on my PC, overlayed it with a fresh 1.5.1, copied the config files into the fresh copy (changing the database and store “demo” name), created another 5.0 database, restored that database from a backup of 1.3.8a’s 5.0 database, and uploaded it into a demo on my server. I downloaded that demo and ran Winmerge against my PC demo file, and they were identical.

I ran zc_install, specified “database upgrade,” and received the following errors:
SKIPPED: Cannot drop index page_accessed on table admin_activity_log because it does not exist.
SKIPPED: Cannot drop index access_date on table admin_activity_log because it does not exist.
SKIPPED: Cannot add index idx_page_accessed_zen to table admin_activity_log because it already exists.
SKIPPED: Cannot add index idx_access_date_zen to table admin_activity_log because it already exists.

I don’t know if the messages above are important, but the admin_activity_log from the SQL dump is:
Before upgrade:

CREATE TABLE `admin_activity_log` (
`log_id` int(15) NOT NULL auto_increment,
`access_date` datetime NOT NULL default '0001-01-01 00:00:00',
`admin_id` int(11) NOT NULL default '0',
`page_accessed` varchar(80) NOT NULL default '',
`page_parameters` text,
`ip_address` varchar(15) NOT NULL default '',
PRIMARY KEY (`log_id`),
KEY `idx_page_accessed_zen` (`page_accessed`),
KEY `idx_access_date_zen` (`access_date`),
KEY `idx_ip_zen` (`ip_address`)
) ENGINE=MyISAM AUTO_INCREMENT=6827 DEFAULT CHARSET=latin1 AUTO_INCREMENT=6827 ;

After upgrade:
CREATE TABLE `admin_activity_log` (
`log_id` bigint(15) NOT NULL auto_increment,
`access_date` datetime NOT NULL default '0001-01-01 00:00:00',
`admin_id` int(11) NOT NULL default '0',
`page_accessed` varchar(80) NOT NULL default '',
`page_parameters` text,
`ip_address` varchar(45) NOT NULL default '',
`flagged` tinyint(4) NOT NULL default '0',
`attention` varchar(255) NOT NULL default '',
`gzpost` mediumblob,
PRIMARY KEY (`log_id`),
KEY `idx_page_accessed_zen` (`page_accessed`),
KEY `idx_access_date_zen` (`access_date`),
KEY `idx_ip_zen` (`ip_address`),
KEY `idx_flagged_zen` (`flagged`)
) ENGINE=MyISAM AUTO_INCREMENT=6841 DEFAULT CHARSET=latin1 AUTO_INCREMENT=6841 ;

I completed the upgrade, received the message about renaming the admin and zc_install, and did so. The demo store looks fine. This time, I received the new sign-in page and it forced me to change my password. However, I have no store options (Configuration, Catalog, Modules, Customers, etc.). I went to “account” via the upper right bar, but it showed only one account (there were 4; it recognizes another sign-in name I tried, so I think it’s a security matter). There’s nothing about “superuser.” It says “(You are presently using: v1.5.1)” under “check for updates,” but when I click on “version” it says “Sorry, your security clearance does not allow you to access this resource.”

Running Winmerge, the 1.5.1 store has a cache file that is different than the 1.3.8 store (I changed the db and password fields to “x” for this post):
installerConfigKeys|a:10:{s:8:"language";s:7:"english";s:16:"DIR_FS_SQL_CACHE";s :62:"/homepages/5/d232125156/htdocs/ohsopersonal.com/store151/cache";s:10:"is_upgrade";s:1:"1";s:7:"DB_TYPE";s:5:"mysql";s:10:"DB_CHARSET";s:4 :"utf8";s:9:"DB_PREFIX";s:0:"";s:9:"DB_SERVER";s:26:"localhost:/tmp/mysql5.sock";s:18:"DB_SERVER_USERNAME";s:12:"dboxxx";s:18:"DB_SERVER_PASSWORD";s :24:"xxx";s:11:"DB_DATABASE";s:11:"dbxxxx";}logfilename|s:27:"Jan-20-2013_09-14-01-etfmCq";

Also missing from the 1.5.1 store: curltest.php, authorizenet.

The old store was running on PHP 5.217, Zen version 1.3.8a, DB patch 1.3.8, MYSQL 5.0. I can’t view the new settings, as per above. My server is with 1and1. (1and1 users: The restore on their MYSQLADMIN doesn’t work. Manually drop the table if it has data, and then use “SQL” option to import instead of following 1and1's published instructions.)

Existing in database (from backup) after upgrade (this is what I’m missing, so I know it's the database):
INSERT INTO `admin_menus` (`menu_key`, `language_key`, `sort_order`) VALUES ('configuration', 'BOX_HEADING_CONFIGURATION', 1),
('catalog', 'BOX_HEADING_CATALOG', 2),
('modules', 'BOX_HEADING_MODULES', 3),
('customers', 'BOX_HEADING_CUSTOMERS', 4),
('taxes', 'BOX_HEADING_LOCATION_AND_TAXES', 5),
('localization', 'BOX_HEADING_LOCALIZATION', 6),
('reports', 'BOX_HEADING_REPORTS', 7),
('tools', 'BOX_HEADING_TOOLS', 8),
('gv', 'BOX_HEADING_GV_ADMIN', 9),
('access', 'BOX_HEADING_ADMIN_ACCESS', 10),
('extras', 'BOX_HEADING_EXTRAS', 11);

Suggestions greatly appreciated.

[rayw1679]

I'm almost afraid to say this, and we're going to test some more, but after several weeks trying to upgrade this store, I think the problem is resolved. My apologies to DrByte for running him crazy; my sincere appreciation for his suggestions. Earlier problems included 1and1's PHPMYADMIN restore not working properly and an apparent failure by FileZilla. Then, I couldn't see the options in admin.

The ID I used to sign-on was not the #1 user, who is apparently the only "Superuser" after conversion. I got the idea from the error in the post above when I tried to view the Version. I signed on with user # 1, all options were available, so I changed all other users to "Superuser." Apparently, if you're not a "Superuser," you can't even see the "Catalog" option for modifying/deleting/adding products, nor any others. I'm going to test for a day or so and then go "live." So, after figuring out what the problem was, it took 15 seconds to resolve.

[dbltoe]

Thanks for coming back and letting everyone know what resolved the issue. By so doing, you'll help someone in the future.

[rayw1679]

Thank you, dbltoe. I'm sure they have it posted somewhere, but I searched under "superuser" and couldn't find it.

The silly thing is that I had that store ready to go 5 days earlier and didn't know it (post #6, but should have said I copied a 1.5.1 store instead of 1.3.9). I just happened to choose the "wrong" logon. After re-loading several times and getting the same error, I assumed it was a database error and reloaded the database, which didn't work. That led to the discovery that 1and1 has a problem with their PHPMYADMIN restore (they are supposed to update their documentation; they thanked me for letting them know). We lost a little info with the restore because I wasn't sure how far back I (thought I) needed to go, but I'm not about to start all that over again. I was considering switching to a commercial system, as I was spending 8 - 14 hours daily on it, not sleeping much, and I was way over my head. I don't like the helpless feeling I get when I don't know what's going wrong.

I finally started trying to figure out PHP code ("Greek" to me) and noticed a "1" with admin in one of the files, so I went back to the original store that was still online to see who the first user was. It was as simple as using the other logon. I suppose on my 1st two conversions I just happened to use the correct one.