[Admin Issue] Upgrading from 2.0.25 to 2.5.0-RC2 - Admin broken, partly solved, still missing some drop-down sub-menus

[JRR]

Well, I starting trying this upgrade months ago, but never had the time to get the bugs ironed out - so the last week I decided that now was the time to deal with it. Man have I wasted a few days on this!

Note, everything here is done on XAMPP localhost environment (OSX). This environment appears to be working properly.

What I've done - starting with a fully functional 2.0.25 site, my main add on was shipping - Canada Post - which added a few items to the database, which seem to fit in with 2.5.x version too, namely product_length, _width, _height, plus a couple of other fields that only Canada Post module worries about.

So thinking that is not going to be a problem I run the upgrade SQL function to bring the 2.0.25 database up to 2.5.0. That works a treat - database goes from 101 fields to 126 fields (two admin spots - one called admin, the other called administrators), and the root OSCMax 'store' works just fine with the updated to 2.5.0 database. Problem is the /admin does not. I get only the top half of the screen - down to the bottom of the menu bar, and a number of sub-menu items are missing. Missing include ALL of the modules sub-menus, Configuration just shows "Google Maps", and Administration is missing a few things in the middle including Site Maintenance.

Now if I CHANGE the database from the modified one, to a database that is 2.5.0, but empty then /admin seems to run just fine...all the drop downs are present, and the screen is full of info (as expected and seen on basic 2.5.0 installations).

So, I'm thinking the problem is more related to either the order of the items in the database or something is missing/present that is being misread by the 2.5.0 admin. Probably another add-on...hmmm...well, when the admin screen was broken it did have 'Security' on the far right, and glancing at that tabs' sub-menus indicated a problem...so I then decided to delete Sitemonitor references from the database and found it hiding in "sessions"! So, I simply deleted all the 'session' data (leaving structure alone of course) and now /admin works much better. Still am missing a number of drop down menus - as above - but I now get a proper screen.

Obviously there is something else in the data bus I have to extract to get it running.

So, if people are having trouble with upgrades, start with your database 'sessions' - back it up, then try deleting the data and see if you now get better operation.

Work in progress...

Images of results so far:

Administration Drop-Down Menu

http://www.flippers.com/images/OSCMa...inistrator.jpg

Catalog Drop-Down Menu

http://www.flippers.com/images/OSCMa...en-Catalog.jpg

Modules Drop-Down Menu

http://www.flippers.com/images/OSCMa...en-Modules.png

Configuration Drop-Down Menu

http://www.flippers.com/images/OSCMa...figuration.jpg

Customers Drop-Down Menu

http://www.flippers.com/images/OSCMa...-Customers.jpg

You need to click on those links because I couldn't upload these pictures as this OSCMax site complained they weren't valid image files!

More problems with database are showing up...undefined variables, etc. lots more work ahead...

[giga009]

Hi there

I too have experienced some of the issues you are dealing with - My post here is Upgrade 2.0.25 t0 2.5.2 issues - Admin Access but no Site - MIssing modules and Site Mtce access

Have you experienced any of the other issues as me ?

I did not have site monitor added only an australian post contribution other than that it was a straight forward install.

I'm very happy (sorry) to find that other people have experienced some of the issues in the Admin area with missing drop downs etc it means that it wasn't me doing anything wrong . Can you access your front cart at all?

Sorry for all the questions ...just trying to sort out this mess I have

Regards giga009

[JRR]

(don't waste your time with this, go to my Sept 19 post for the solution - JRR)

Well, digging further it appears that somehow the links for the missing drop-down menu items can be rebuilt if you use the "File Access" sub-menu. I have managed to reconstruct some of the Administrator, need to make a list of all the options for each selection so I can link the proper xxx.php files to the correct drop-down menu.

So, first go to the 'Administrator', then open the drop-down 'File Access', then double-click on the 'Administrator' folder and you will see what files are supposed to be present. If any do not show in the drop-down menu, or shouldn't be there, then delete them and move them to the correct drop-down menu later.

I've made a bunch of images of the various pull-down menus you see in the base 2.5.2 admin (zipped file just below). Would be nice if there was a list somewhere for consulting...what I'd like to see is a list of the variables used and an expanded text menu structure - this would simplify the job of upgrading IMHO.

http://www.flippers.com/images/OSCMa...AdminMenus.zip

John :-#)#

[JRR]

(yeah, don't worry about this post either - the next one is the solution! JRR)

Further digging shows that the database file has somehow not gotten fully upgraded. Structure for the admin bar (as found in the backup file of a working 2.5.2 system) looks like this:

insert into admin_files (admin_files_id, admin_files_name, admin_display_name, admin_files_is_boxes, admin_files_to_boxes, admin_groups_id, admin_sort_order) values ('1', 'administrator.php', 'BOX_HEADING_ADMINISTRATOR', '1', '0', '1', '1');
insert into admin_files (admin_files_id, admin_files_name, admin_display_name, admin_files_is_boxes, admin_files_to_boxes, admin_groups_id, admin_sort_order) values ('2', 'configuration.php', 'BOX_HEADING_CONFIGURATION', '1', '0', '1', '2');


Whereas what I have in my supposedly upgraded to 2.5.2 database is this structure for the same first few lines:

insert into admin_files (admin_files_id, admin_files_name, admin_files_is_boxes, admin_files_to_boxes, admin_groups_id) values ('1', 'administrator.php', '1', '0', '1,2');
insert into admin_files (admin_files_id, admin_files_name, admin_files_is_boxes, admin_files_to_boxes, admin_groups_id) values ('2', 'configuration.php', '1', '0', '1');



Note the missing field - "admin_display_name" and the different admin_groups_id numbers (not sure what they represent).

And that is found in 2.0.25_To_2.5.0.sql which is the 1st upgrade I ran. Must have been a bad upgrade process.

Now at least I know what to look for after doing the initial conversion from 2.0.25 to 2.5.0-RC2, if the admin directory doesn't have those variables, then it wasn't upgraded properly.

Hope this info helps someone - may be rambling, but I believe the info is useful...

[JRR]

SOLVED!

There is a problem with the 2.0.25_To_2.5.0.sql upgrade script as found on OSCMax download page Upgrade Script for v2.0.25 users ONLY!83.71 KB (v2025-to-250-upgrade.zip)

The first lines read:

/*
osCmax v2.0.25 to v2.5.0 Database upgrade script.
************************************************** *******************
*/
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;


/* Alter table in target */

However they should read:

/*
/* osCmax v2.0.25 to v2.5.0 Database upgrade script. (Fixed JRR) */
/************************************************** *******************/
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

/* Alter table in target */

Note the added '/'s...(you can delete the "Fixed JRR" - I won't be offended!)

Phew - you don't want to know how much time I wasted trying to get upgraded, days and days and days...if only I could read PHP!

John :-#)#