Error after upgrade

[Mary]

We upgraded from 2.3.x to 2.6.x and now when I go to administration-phocagallery-users and try to "authorize all" I get the following error

Error while authorizing all categories and images

http://www.brugmansia.us/content/admini ... lleryusers

[Jan]

Hi, try to check if all tables are installed in database, see install.bak file in ZIP installation file and compare it to your database e.g. via phpMyAdmin.

Jan

[Mary]

I did that and all tables are there. Can I PM you the username/password and you look at it for me?

[pdenessen]

Hi ,

I had a similair problem when upgrading from 2.5.1 to 2.6.1
I checked the tables and the install.bak file which is in the 2.6.1 zip file.

I found some mistakes in the listing;
from several lines the word ADD is missing,
the field published is missing in the phocagallery and phocagallery_categories tables.

Below you find my comments where the changed lines are marked with --*

Since I am not an MySQL expert, I also discoverd that some fields in some tables had another order has in the original installation scrip.
Is this important ?

I alsoo discovered that after the upgrade and the fixing of the tables, no categories where displayed in the frontend. When I added a new categorie in the backend, this was displayed in the frontend. I assume that certain tables or files needs to be re-indexed.
Who can help here ?

@Jan : Perhaps you can add in the next release a script, just like in CB, which checks and fixes the tables.

Code: Select all

-- 2.6.0
-- ALTER TABLE `#__phocagallery` ADD `imgorigsize` int(11) NOT NULL default '0' AFTER `hits` ;
-- ALTER TABLE `#__phocagallery_categories` ADD `owner_id` int(11) NOT NULL default '0' AFTER `parent_id` ;
--* ALTER TABLE `#__phocagallery` ADD `extid` varchar(255) NOT NULL default '' AFTER `hits` ;
--* ALTER TABLE `#__phocagallery` ADD `extl` varchar(255) NOT NULL default '' AFTER `hits` ;
--* ALTER TABLE `#__phocagallery` ADD `extm` varchar(255) NOT NULL default '' AFTER `hits` ;
--* ALTER TABLE `#__phocagallery` ADD  `exts` varchar(255) NOT NULL default '' AFTER `hits` ;
--* ALTER TABLE `#__phocagallery` ADD `exto` varchar(255) NOT NULL default '' AFTER `hits` ;
--* ALTER TABLE `#__phocagallery` ADD `extw` varchar(255) NOT NULL default '' AFTER `hits` ;
--* ALTER TABLE `#__phocagallery` ADD `exth` varchar(255) NOT NULL default '' AFTER `hits` ;

-- ALTER TABLE `#__phocagallery_categories` ADD `extid` varchar(255) NOT NULL default '' AFTER `hits` ;
-- ALTER TABLE `#__phocagallery_categories` ADD `exta` varchar(255) NOT NULL default '' AFTER `hits` ;
-- ALTER TABLE `#__phocagallery_categories` ADD `extu` varchar(255) NOT NULL default '' AFTER `hits` ;

-- missing lines
--* ALTER TABLE `#__phocagallery` ADD `approved` tinyint(1) NOT NULL default '0' AFTER `imgorigsize`; 
--* ALTER TABLE `#__phocagallery_categories` ADD `approved` tinyint(1) NOT NULL default '0' AFTER `published` ;  

[Jan]

Hi,

Since I am not an MySQL expert, I also discoverd that some fields in some tables had another order has in the original installation scrip.
Is this important ?

No, does not matter.

Thanks for the information. Yes the approved information is missed there, I will fix it.

Perhaps you can add in the next release a script, just like in CB, which checks and fixes the tables

For now I will not change the upgrade script as upgrading feature will be changed in Joomla! 1.6 so I hope the upgrade feature can be used then.

Jan