Upgrade to 3.0 disaster but database 2.5 fixed by euoceo!!!

Need help upgrading your Joomla! website or converting to Joomla! 3.x?

Moderator: General Support Moderators

Forum rules
Forum Rules
Absolute Beginner's Guide to Joomla! <-- please read before posting, this means YOU.
Forum Post Assistant - If you are serious about wanting help, you will use this tool to help you post.
Locked
chadgarber
Joomla! Apprentice
Joomla! Apprentice
Posts: 17
Joined: Sat May 08, 2010 1:04 am

Upgrade to 3.0 disaster but database 2.5 fixed by euoceo!!!

Post by chadgarber » Mon Oct 01, 2012 11:06 pm

I upgraded to 3.0, it was a disaster, so I rolled back to 2.5.7 by restoring the files from GoDaddy backup, but now when I go to the home page, I get an Error: 500 message followed by an incredibly long message. Also, when I am in the back end, and click on one of the menus, it does the same error message. I went to extension manager, database, and I clicked fix but it leaves the following:

Warning: Database is not up to date!
2 Database Problems Found
Table 'ekjj_content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.3-2011-10-15.sql.)
Table 'ekjj_content' does not have column 'title_alias' with type 'VARCHAR(255)'. (From file 1.7.4-2011-11-23.sql.)

I turned on debugging and I get the following.
Call stack
# Function Location
1 JAdministrator->dispatch() /home/content/66/5614266/html/mainsite/administrator/index.php:46
2 JComponentHelper::renderComponent() /home/content/66/5614266/html/mainsite/administrator/includes/application.php:153
3 JComponentHelper::executeComponent() /home/content/66/5614266/html/mainsite/libraries/joomla/application/component/helper.php:351
4 require_once() /home/content/66/5614266/html/mainsite/libraries/joomla/application/component/helper.php:383
5 JController->execute() /home/content/66/5614266/html/mainsite/administrator/components/com_menus/menus.php:18
6 MenusController->display() /home/content/66/5614266/html/mainsite/libraries/joomla/application/component/controller.php:761
7 JController->display() /home/content/66/5614266/html/mainsite/administrator/components/com_menus/controller.php:58
8 MenusViewItems->display() /home/content/66/5614266/html/mainsite/libraries/joomla/application/component/controller.php:722
9 JView->get() /home/content/66/5614266/html/mainsite/administrator/components/com_menus/views/items/view.html.php:34
10 JModelList->getItems() /home/content/66/5614266/html/mainsite/libraries/joomla/application/component/view.php:386
11 JModelList->getStart() /home/content/66/5614266/html/mainsite/libraries/joomla/application/component/modellist.php:128
12 JModelList->getTotal() /home/content/66/5614266/html/mainsite/libraries/joomla/application/component/modellist.php:265
13 JModel->_getListCount() /home/content/66/5614266/html/mainsite/libraries/joomla/application/component/modellist.php:231
14 JDatabaseMySQL->execute() /home/content/66/5614266/html/mainsite/libraries/joomla/application/component/model.php:318
15 JError::raiseError() /home/content/66/5614266/html/mainsite/libraries/joomla/database/database/mysql.php:548
16 JError::raise() /home/content/66/5614266/html/mainsite/libraries/joomla/error/error.php:251

The long error message is:
JDatabaseMySQL::query: 1054 - Unknown column 'a.title_alias' in 'field list' SQL=SELECT a.id, a.title, a.alias, a.title_alias, a.introtext, a.checked_out, a.checked_out_time, a.catid, a.created, a.created_by, a.created_by_alias, CASE WHEN a.modified = 0 THEN a.created ELSE a.modified END as modified, a.modified_by, uam.name as modified_by_name,CASE WHEN a.publish_up = 0 THEN a.created ELSE a.publish_up END as publish_up,a.publish_down, a.images, a.urls, a.attribs, a.metadata, a.metakey, a.metadesc, a.access, a.hits, a.xreference, a.featured, LENGTH(a.fulltext) AS readmore,CASE WHEN badcats.id is not null THEN 0 ELSE a.state END AS state,c.title AS category_title, c.path AS category_route, c.access AS category_access, c.alias AS category_alias,CASE WHEN a.created_by_alias > ' ' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,contact.id as contactid,parent.title as parent_title, parent.id as parent_id, parent.path as parent_route, parent.alias as parent_alias,ROUND(v.rating_sum / v.rating_count, 0) AS rating, v.rating_count as rating_count,c.published, CASE WHEN badcats.id is null THEN c.published ELSE 0 END AS parents_published FROM ekjj_content AS a LEFT JOIN ekjj_content_frontpage AS fp ON fp.content_id = a.id LEFT JOIN ekjj_categories AS c ON c.id = a.catid LEFT JOIN ekjj_users AS ua ON ua.id = a.created_by LEFT JOIN ekjj_users AS uam ON uam.id = a.modified_by LEFT JOIN ( SELECT contact.user_id, MAX(contact.id) AS id, contact.language FROM ekjj_contact_details AS contact WHERE contact.published = 1 GROUP BY contact.user_id, contact.language) AS contact ON contact.user_id = a.created_by LEFT JOIN ekjj_categories as parent ON parent.id = c.parent_id LEFT JOIN ekjj_content_rating AS v ON a.id = v.content_id LEFT OUTER JOIN (SELECT cat.id as id FROM ekjj_categories AS cat JOIN ekjj_categories AS parent ON cat.lft BETWEEN parent.lft AND parent.rgt WHERE parent.extension = 'com_content' AND parent.published != 1 GROUP BY cat.id ) AS badcats ON badcats.id = c.id WHERE a.access IN (1,1) AND c.access IN (1,1) AND CASE WHEN badcats.id is null THEN a.state ELSE 0 END = 1 AND a.catid = 83 AND (a.publish_up = '0000-00-00 00:00:00' OR a.publish_up <= '2012-10-01 22:57:18') AND (a.publish_down = '0000-00-00 00:00:00' OR a.publish_down >= '2012-10-01 22:57:18') GROUP BY a.id, a.title, a.alias, a.title_alias, a.introtext, a.checked_out, a.checked_out_time, a.catid, a.created, a.created_by, a.created_by_alias, a.created, a.modified, a.modified_by, uam.name, a.publish_up, a.attribs, a.metadata, a.metakey, a.metadesc, a.access, a.hits, a.xreference, a.featured, a.fulltext, a.state, a.publish_down, badcats.id, c.title, c.path, c.access, c.alias, uam.id, ua.name, ua.email, contact.id, parent.title, parent.id, parent.path, parent.alias, v.rating_sum, v.rating_count, c.published, c.lft, a.ordering, parent.lft, fp.ordering, c.id, a.images, a.urls ORDER BY c.lft, a.ordering, a.created LIMIT 0, 2

Any help would be appreciated. (Note: It worked fine before the 3.0 upgrade)
ALSO: Here is the system information:
System Information
Setting Value

PHP Built On Linux p3nlhg290.shr.prod.phx3.secureserver.net 2.6.32-279.2.1.el6.x86_64 #1 SMP Fri Jul 20 01:55:29 UTC 2012 x86_64
Database Version 5.0.92-log
Database Collation utf8_general_ci
PHP Version 5.3.14
Web Server Apache
WebServer to PHP Interface cgi-fcgi
Joomla! Version Joomla! 2.5.7 Stable [ Ember ] 13-September-2012 14:00 GMT
Joomla! Platform Version Joomla Platform 11.4.0 Stable [ Brian Kernighan ] 03-Jan-2012 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.79 Safari/537.4
Last edited by chadgarber on Tue Oct 02, 2012 10:39 pm, edited 1 time in total.

User avatar
euoceo
Joomla! Guru
Joomla! Guru
Posts: 955
Joined: Fri Sep 12, 2008 2:48 pm
Location: Sacramento
Contact:

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by euoceo » Tue Oct 02, 2012 6:03 am

Did you also restore the databaseback to 2.5? Why did you upgrade to 3.0? It is clearly stated to skip this release on a production system!
Joomla! Web Hosting, Design, and Consulting.
Portfolio: http://www.calweb.com/joomla
Please do not PM me for help, use the forums first.

sovainfo
Joomla! Exemplar
Joomla! Exemplar
Posts: 8808
Joined: Sat Oct 01, 2011 7:06 pm

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by sovainfo » Tue Oct 02, 2012 7:41 am

Also for j3 you need mysql 5.1, so you can't upgrade!
Issue with migrating? Include logs/joomla_update.php in your report!
Blank screen? Verify pagesource for HTML code (javascript error)
Installation failing on populating database? Install with set_time_limit(0)
Document your customizations!

chadgarber
Joomla! Apprentice
Joomla! Apprentice
Posts: 17
Joined: Sat May 08, 2010 1:04 am

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by chadgarber » Tue Oct 02, 2012 2:08 pm

euoceo wrote:Did you also restore the databaseback to 2.5? Why did you upgrade to 3.0? It is clearly stated to skip this release on a production system!
It was suggested to upgrade in the Joomla Admin tools...I didn't go to Joomla.org to see if I should or not since I THOUGHT it was USUALLY safe to upgrade something suggested by Joomla Admin Tools or Joomla's built in Update component. I was having some other issues and figured perhaps an update would help. Wrong.

I am having trouble finding a backup of the database back when it was 2.5. Is there any way to fix the 3.0 database to work with 2.5 again, like some kind of downgrade 3.0 to 2.5 database tool?

chadgarber
Joomla! Apprentice
Joomla! Apprentice
Posts: 17
Joined: Sat May 08, 2010 1:04 am

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by chadgarber » Tue Oct 02, 2012 2:11 pm

sovainfo wrote:Also for j3 you need mysql 5.1, so you can't upgrade!
I suppose maybe that is why it failed. Can't I upgrade my mysql to 5.1 on Godaddy?

chadgarber
Joomla! Apprentice
Joomla! Apprentice
Posts: 17
Joined: Sat May 08, 2010 1:04 am

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by chadgarber » Tue Oct 02, 2012 2:56 pm

Here is the mysql 3.0 update file. Surely there is an undo version:
ALTER TABLE `#__users` DROP KEY `usertype`;
ALTER TABLE `#__session` DROP KEY `whosonline`;

DROP TABLE IF EXISTS `#__update_categories`;

ALTER TABLE `#__contact_details` DROP `imagepos`;
ALTER TABLE `#__content` DROP COLUMN `title_alias`;
ALTER TABLE `#__content` DROP COLUMN `sectionid`;
ALTER TABLE `#__content` DROP COLUMN `mask`;
ALTER TABLE `#__content` DROP COLUMN `parentid`;
ALTER TABLE `#__newsfeeds` DROP COLUMN `filename`;
ALTER TABLE `#__weblinks` DROP COLUMN `sid`;
ALTER TABLE `#__weblinks` DROP COLUMN `date`;
ALTER TABLE `#__weblinks` DROP COLUMN `archived`;
ALTER TABLE `#__weblinks` DROP COLUMN `approved`;
ALTER TABLE `#__menu` DROP COLUMN `ordering`;
ALTER TABLE `#__session` DROP COLUMN `usertype`;
ALTER TABLE `#__users` DROP COLUMN `usertype`;
ALTER TABLE `#__updates` DROP COLUMN `categoryid`;

UPDATE `#__extensions` SET protected = 0 WHERE
`name` = 'com_search' OR
`name` = 'mod_articles_archive' OR
`name` = 'mod_articles_latest' OR
`name` = 'mod_banners' OR
`name` = 'mod_feed' OR
`name` = 'mod_footer' OR
`name` = 'mod_users_latest' OR
`name` = 'mod_articles_category' OR
`name` = 'mod_articles_categories' OR
`name` = 'plg_content_pagebreak' OR
`name` = 'plg_content_pagenavigation' OR
`name` = 'plg_content_vote' OR
`name` = 'plg_editors_tinymce' OR
`name` = 'plg_system_p3p' OR
`name` = 'plg_user_contactcreator' OR
`name` = 'plg_user_profile';

DELETE FROM `#__extensions` WHERE `extension_id` = 800;

ALTER TABLE `#__assets` ENGINE=InnoDB;
ALTER TABLE `#__associations` ENGINE=InnoDB;
ALTER TABLE `#__banners` ENGINE=InnoDB;
ALTER TABLE `#__banner_clients` ENGINE=InnoDB;
ALTER TABLE `#__banner_tracks` ENGINE=InnoDB;
ALTER TABLE `#__categories` ENGINE=InnoDB;
ALTER TABLE `#__contact_details` ENGINE=InnoDB;
ALTER TABLE `#__content` ENGINE=InnoDB;
ALTER TABLE `#__content_frontpage` ENGINE=InnoDB;
ALTER TABLE `#__content_rating` ENGINE=InnoDB;
ALTER TABLE `#__core_log_searches` ENGINE=InnoDB;
ALTER TABLE `#__extensions` ENGINE=InnoDB;
ALTER TABLE `#__finder_filters` ENGINE=InnoDB;
ALTER TABLE `#__finder_links` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms0` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms1` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms2` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms3` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms4` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms5` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms6` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms7` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms8` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_terms9` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_termsa` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_termsb` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_termsc` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_termsd` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_termse` ENGINE=InnoDB;
ALTER TABLE `#__finder_links_termsf` ENGINE=InnoDB;
ALTER TABLE `#__finder_taxonomy` ENGINE=InnoDB;
ALTER TABLE `#__finder_taxonomy_map` ENGINE=InnoDB;
ALTER TABLE `#__finder_terms` ENGINE=InnoDB;
ALTER TABLE `#__finder_terms_common` ENGINE=InnoDB;
ALTER TABLE `#__finder_types` ENGINE=InnoDB;
ALTER TABLE `#__languages` ENGINE=InnoDB;
ALTER TABLE `#__menu` ENGINE=InnoDB;
ALTER TABLE `#__menu_types` ENGINE=InnoDB;
ALTER TABLE `#__messages` ENGINE=InnoDB;
ALTER TABLE `#__messages_cfg` ENGINE=InnoDB;
ALTER TABLE `#__modules` ENGINE=InnoDB;
ALTER TABLE `#__modules_menu` ENGINE=InnoDB;
ALTER TABLE `#__newsfeeds` ENGINE=InnoDB;
ALTER TABLE `#__overrider` ENGINE=InnoDB;
ALTER TABLE `#__redirect_links` ENGINE=InnoDB;
ALTER TABLE `#__schemas` ENGINE=InnoDB;
ALTER TABLE `#__session` ENGINE=InnoDB;
ALTER TABLE `#__template_styles` ENGINE=InnoDB;
ALTER TABLE `#__updates` ENGINE=InnoDB;
ALTER TABLE `#__update_sites` ENGINE=InnoDB;
ALTER TABLE `#__update_sites_extensions` ENGINE=InnoDB;
ALTER TABLE `#__users` ENGINE=InnoDB;
ALTER TABLE `#__usergroups` ENGINE=InnoDB;
ALTER TABLE `#__user_notes` ENGINE=InnoDB;
ALTER TABLE `#__user_profiles` ENGINE=InnoDB;
ALTER TABLE `#__user_usergroup_map` ENGINE=InnoDB;
ALTER TABLE `#__viewlevels` ENGINE=InnoDB;
ALTER TABLE `#__weblinks` ENGINE=InnoDB;

ALTER TABLE `#__weblinks` ADD COLUMN `version` int(10) unsigned NOT NULL DEFAULT '1';
ALTER TABLE `#__weblinks` ADD COLUMN `images` text NOT NULL;
ALTER TABLE `#__newsfeeds` ADD COLUMN `description` text NOT NULL;
ALTER TABLE `#__newsfeeds` ADD COLUMN `version` int(10) unsigned NOT NULL DEFAULT '1';
ALTER TABLE `#__newsfeeds` ADD COLUMN `hits` int(10) unsigned NOT NULL DEFAULT '0';
ALTER TABLE `#__newsfeeds` ADD COLUMN `images` text NOT NULL;
ALTER TABLE `#__contact_details` ADD COLUMN `version` int(10) unsigned NOT NULL DEFAULT '1';
ALTER TABLE `#__contact_details` ADD COLUMN `hits` int(10) unsigned NOT NULL DEFAULT '0';
ALTER TABLE `#__banners` ADD COLUMN `created_by` int(10) unsigned NOT NULL DEFAULT '0';
ALTER TABLE `#__banners` ADD COLUMN `created_by_alias` varchar(255) NOT NULL DEFAULT '';
ALTER TABLE `#__banners` ADD COLUMN `modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00';
ALTER TABLE `#__banners` ADD COLUMN `modified_by` int(10) unsigned NOT NULL DEFAULT '0';
ALTER TABLE `#__banners` ADD COLUMN `version` int(10) unsigned NOT NULL DEFAULT '1';
ALTER TABLE `#__categories` ADD COLUMN `version` int(10) unsigned NOT NULL DEFAULT '1';
UPDATE `#__assets` SET name=REPLACE( name, 'com_user.notes.category','com_users.category' );
UPDATE `#__categories` SET extension=REPLACE( extension, 'com_user.notes.category','com_users.category' );

ALTER TABLE `#__finder_terms` ADD COLUMN `language` char(3) NOT NULL DEFAULT '';
ALTER TABLE `#__finder_tokens` ADD COLUMN `language` char(3) NOT NULL DEFAULT '';
ALTER TABLE `#__finder_tokens_aggregate` ADD COLUMN `language` char(3) NOT NULL DEFAULT '';

INSERT INTO `#__extensions`
(`name`, `type`, `element`, `folder`, `client_id`, `enabled`, `access`, `protected`, `manifest_cache`, `params`, `custom_data`, `system_data`, `checked_out`, `checked_out_time`, `ordering`, `state`)
VALUES
('isis', 'template', 'isis', '', 1, 1, 1, 0, '{"name":"isis","type":"template","creationDate":"3\\/30\\/2012","author":"Kyle Ledbetter","copyright":"Copyright (C) 2005 - 2012 Open Source Matters, Inc. All rights reserved.","authorEmail":"admin@joomla.org","authorUrl":"","version":"1.0","description":"TPL_ISIS_XML_DESCRIPTION","group":""}', '{"templateColor":"","logoFile":""}', '', '', 0, '0000-00-00 00:00:00', 0, 0),
('protostar', 'template', 'protostar', '', 0, 1, 1, 0, '{"name":"protostar","type":"template","creationDate":"4\\/30\\/2012","author":"Kyle Ledbetter","copyright":"Copyright (C) 2005 - 2012 Open Source Matters, Inc. All rights reserved.","authorEmail":"admin@joomla.org","authorUrl":"","version":"1.0","description":"TPL_PROTOSTAR_XML_DESCRIPTION","group":""}', '{"templateColor":"","logoFile":"","googleFont":"1","googleFontName":"Open+Sans","fluidContainer":"0"}', '', '', 0, '0000-00-00 00:00:00', 0, 0),
('beez3', 'template', 'beez3', '', 0, 1, 1, 0, '{"legacy":false,"name":"beez3","type":"template","creationDate":"25 November 2009","author":"Angie Radtke","copyright":"Copyright (C) 2005 - 2012 Open Source Matters, Inc. All rights reserved.","authorEmail":"a.radtke@derauftritt.de","authorUrl":"http:\\/\\/www.der-auftritt.de","version":"1.6.0","description":"TPL_BEEZ3_XML_DESCRIPTION","group":""}', '{"wrapperSmall":"53","wrapperLarge":"72","sitetitle":"","sitedescription":"","navposition":"center","templatecolor":"nature"}', '', '', 0, '0000-00-00 00:00:00', 0, 0);

INSERT INTO `#__template_styles` (`template`, `client_id`, `home`, `title`, `params`) VALUES
('protostar', 0, '0', 'protostar - Default', '{"templateColor":"","logoFile":"","googleFont":"1","googleFontName":"Open+Sans","fluidContainer":"0"}'),
('isis', 1, '1', 'isis - Default', '{"templateColor":"","logoFile":""}'),
('beez3', 0, '0', 'beez3 - Default', '{"wrapperSmall":53,"wrapperLarge":72,"logo":"","sitetitle":"","sitedescription":"","navposition":"center","bootstrap":"","templatecolor":"nature","headerImage":"","backgroundcolor":"#eee"}');

UPDATE `#__template_styles`
SET home = (CASE WHEN (SELECT count FROM (SELECT count(`id`) AS count
FROM `#__template_styles`
WHERE home = '1'
AND client_id = 1) as c) = 0
THEN '1'
ELSE '0'
END)
WHERE template = 'isis'
AND home != '1';

UPDATE `#__template_styles`
SET home = 0
WHERE template = 'bluestork';

INSERT INTO `#__extensions` (`extension_id`, `name`, `type`, `element`, `folder`, `client_id`, `enabled`, `access`, `protected`, `manifest_cache`, `params`, `custom_data`, `system_data`, `checked_out`, `checked_out_time`, `ordering`, `state`) VALUES
(315, 'mod_stats_admin', 'module', 'mod_stats_admin', '', 1, 1, 1, 0, '{"name":"mod_stats_admin","type":"module","creationDate":"September 2012","author":"Joomla! Project","copyright":"Copyright (C) 2005 - 2012 Open Source Matters. All rights reserved.","authorEmail":"admin@joomla.org","authorUrl":"www.joomla.org","version":"3.0.0","description":"MOD_STATS_XML_DESCRIPTION","group":""}', '{"serverinfo":"0","siteinfo":"0","counter":"0","increase":"0","cache":"1","cache_time":"900","cachemode":"static"}', '', '', 0, '0000-00-00 00:00:00', 0, 0);

UPDATE `#__update_sites`
SET location = 'http://update.joomla.org/language/translationlist_3.xml'
WHERE location = 'http://update.joomla.org/language/translationlist.xml'
AND name = 'Accredited Joomla! Translations';

User avatar
euoceo
Joomla! Guru
Joomla! Guru
Posts: 955
Joined: Fri Sep 12, 2008 2:48 pm
Location: Sacramento
Contact:

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by euoceo » Tue Oct 02, 2012 4:00 pm

There's probably no undo, it's always suggested to backup the site/DB before upgrading. Granted it's probably ignored for minor .x changes, but never ever when popping up a to a new version line!

Ask godaddy if they can restore your DB from a backup. They should be able to do that, hosting over 5 million websites should mean they probably had to have done that a few times already. :D
Joomla! Web Hosting, Design, and Consulting.
Portfolio: http://www.calweb.com/joomla
Please do not PM me for help, use the forums first.

chadgarber
Joomla! Apprentice
Joomla! Apprentice
Posts: 17
Joined: Sat May 08, 2010 1:04 am

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by chadgarber » Tue Oct 02, 2012 4:32 pm

euoceo wrote:There's probably no undo, it's always suggested to backup the site/DB before upgrading. Granted it's probably ignored for minor .x changes, but never ever when popping up a to a new version line!

Ask godaddy if they can restore your DB from a backup. They should be able to do that, hosting over 5 million websites should mean they probably had to have done that a few times already. :D
Thanks, just did. They say for $150.00 they will restore it. Unbelievable.

User avatar
euoceo
Joomla! Guru
Joomla! Guru
Posts: 955
Joined: Fri Sep 12, 2008 2:48 pm
Location: Sacramento
Contact:

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by euoceo » Tue Oct 02, 2012 5:06 pm

Wow! That is total BS... On a bad day I'll charge $25 and if it's a frequent occurrence from the customer, but usually it's free. I'm guessing 1/2 that fee goes to Danica Patrick. lol...
Joomla! Web Hosting, Design, and Consulting.
Portfolio: http://www.calweb.com/joomla
Please do not PM me for help, use the forums first.

chadgarber
Joomla! Apprentice
Joomla! Apprentice
Posts: 17
Joined: Sat May 08, 2010 1:04 am

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by chadgarber » Tue Oct 02, 2012 8:25 pm

euoceo wrote:Wow! That is total BS... On a bad day I'll charge $25 and if it's a frequent occurrence from the customer, but usually it's free. I'm guessing 1/2 that fee goes to Danica Patrick. lol...
Well what's worse is that they say it will take 7 to 10 days!!!!!!!!!!!!!

chadgarber
Joomla! Apprentice
Joomla! Apprentice
Posts: 17
Joined: Sat May 08, 2010 1:04 am

Re: Upgraded to 3.0 was a disaster, rolled back to 2.7 but..

Post by chadgarber » Tue Oct 02, 2012 10:37 pm

chadgarber wrote:
euoceo wrote:Wow! That is total BS... On a bad day I'll charge $25 and if it's a frequent occurrence from the customer, but usually it's free. I'm guessing 1/2 that fee goes to Danica Patrick. lol...
Well what's worse is that they say it will take 7 to 10 days!!!!!!!!!!!!!
Yes, euoceo saved the day and got my database and website back up in a very short time. Awesome work.

User avatar
euoceo
Joomla! Guru
Joomla! Guru
Posts: 955
Joined: Fri Sep 12, 2008 2:48 pm
Location: Sacramento
Contact:

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by euoceo » Tue Oct 02, 2012 11:02 pm

7 to 10 days??? OMG, how can they even consider that a $150 service!

Thanks for the nice words, glad to have helped.

Here's what I did for anyone else that might land on this thread:
First I imported your dump.sql into a new DB (J30). Then exported J30 (less the virtuemart tables) telling phpmysqladmin to not put in table creation info in the dump.

Next I installed a clean version of 2.5.7 on my local test server, used your unique table prefix for the DB and then emptied out all the tables.

Then did several imports addressing each new error, truncating tables again and re-importing again. The errors were mostly confined to new columns in a few tables. Added those columns and imported. When all done those new columns were dropped for 2.5 (even though they're not used) compatibility.

The big changes were in those 3 tables (banners, weblinks, and newsfeeds) that thankfully are not used a whole lot and don't contain articles or much content so I removed those from the dump.sql.

Lastly I exported the virtuemart tables from the dump.sql DB and then imported those to the 2.5 DB. Then an export to work1.sql as the final dump which I used to import to your website.
Joomla! Web Hosting, Design, and Consulting.
Portfolio: http://www.calweb.com/joomla
Please do not PM me for help, use the forums first.

User avatar
humvee
Joomla! Master
Joomla! Master
Posts: 14713
Joined: Wed Aug 17, 2005 10:27 pm
Location: Kent, England

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by humvee » Wed Oct 03, 2012 11:17 am

[Mod note: Moved from Installation Forum to Upgrade Forum; ]
To help you, in the future, find the correct forum for your topic please read the Which forum to post your question that I have put together.

Two very simple solutions to the problems you caused.

[list=1]
[*]Create a backup of the site and database BEFORE any update, Extensions installation or edits of ACL and core code (last not recommended at all).
[*]Don't upgrade to 3.x until the 3.5 LTS release in two years time unless you are advance adopter, experienced user, or developer![/list]

underlandtongue
Joomla! Fledgling
Joomla! Fledgling
Posts: 3
Joined: Mon Nov 19, 2012 10:20 pm

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by underlandtongue » Mon Nov 19, 2012 10:27 pm

Hello!

I too, am in need of help. Euoceo if you are as advertised, I would LOVE some of that help!

Similarly, I have a site that I updated to 3.0. Yes, thanks for the reminder of everything I didn't do and am still kicking myself for. (After all these years w/ Joomla, you'd think I'd learn).

Nevertheless, I have a conflict with 3.0. I have successfully updated from 1.5 all the way up...with nary a problem. Sure, I'd have the occasional plug in that wouldn't cooperate but that was nothing like what I saw in 3.0! It seems to have changed my folder structure as well as updating files.

I am also on GoDaddy (easy and cheap domain registration) for this site.

I can't figure out how to fix this error:

Fatal error: Cannot redeclare class JDatabaseInterface in /home/content/87/9628387/html/joomla/libraries/joomla/database/driver.php on line 23

(I was able to locate the file, but cannot find the other function that is conflicting with the JDI and causing it to declare two classes of the JDI)

http://www.tucknologies.com/joomla

(Joomla for my main site. I have other subs and directories on the root)

I can provide any administrative access as needed, and any contact information.

underlandtongue
Joomla! Fledgling
Joomla! Fledgling
Posts: 3
Joined: Mon Nov 19, 2012 10:20 pm

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by underlandtongue » Wed Nov 21, 2012 1:22 pm

Another great fix thanks to euoceo!

I had almost given up hope and thought I'd have to start over again, but he was able to get the site back from the install back to a restored state.

Hurray!

I couldn't be more pleased with his service, help or demeanor. It was a pleasure to work with him. :)

BPivo
Joomla! Fledgling
Joomla! Fledgling
Posts: 1
Joined: Fri Jan 11, 2013 1:47 pm

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by BPivo » Fri Jan 11, 2013 1:51 pm

euoceo wrote:7 to 10 days??? OMG, how can they even consider that a $150 service!

Thanks for the nice words, glad to have helped.

Here's what I did for anyone else that might land on this thread:
First I imported your dump.sql into a new DB (J30). Then exported J30 (less the virtuemart tables) telling phpmysqladmin to not put in table creation info in the dump.

Next I installed a clean version of 2.5.7 on my local test server, used your unique table prefix for the DB and then emptied out all the tables.

Then did several imports addressing each new error, truncating tables again and re-importing again. The errors were mostly confined to new columns in a few tables. Added those columns and imported. When all done those new columns were dropped for 2.5 (even though they're not used) compatibility.

The big changes were in those 3 tables (banners, weblinks, and newsfeeds) that thankfully are not used a whole lot and don't contain articles or much content so I removed those from the dump.sql.

Lastly I exported the virtuemart tables from the dump.sql DB and then imported those to the 2.5 DB. Then an export to work1.sql as the final dump which I used to import to your website.

Did you also replaced the Joomla files on the FTP server, with the files of version 2.5?

Adnet
Joomla! Enthusiast
Joomla! Enthusiast
Posts: 135
Joined: Wed Nov 24, 2010 8:52 am
Location: Greece
Contact:

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by Adnet » Fri Jun 13, 2014 5:43 pm

I have exactly the same problem here.

Anyone can help ?

User avatar
euoceo
Joomla! Guru
Joomla! Guru
Posts: 955
Joined: Fri Sep 12, 2008 2:48 pm
Location: Sacramento
Contact:

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by euoceo » Fri Aug 08, 2014 5:15 pm

Just a note, the above instructions are somewhat out of date, though the idea/procedures (more tables affected) still apply as I recently had to fix another 2.5 site that upgraded to 3.3.1 and had a broken website/DB afterwards. There are several more DB changes then what are listed above and backing out and restoring the DB back to a 2.5.x site is not a simple task. There are also new tables that need to be removed and if/when you plan to upgrade to 3.x there are table entries that also need to be deleted otherwise the next upgrade fails with duplicate key errors.

Here's an updated step-by-step for you:

1. As noted many times, DO NO upgrade to these interim releases if you are on 2.5 and a production website.
2. Should you get that burning sensation to upgrade anyways refer to step 2.
3. Should you not follow steps 1 and 2, and decide to upgrade ALWAYS backup your site's root files AND do a database backup of your current site.
4. Upgrade fails? Restore files from step 3.
5. Upgraded fails, no backups? Contact your ISP next, sometimes they have backups that are separate from yours. Expect a small charge and possibly a delay (up to 7 days according to a godaddy post above).
6. No backups either by you or ISP? Unless you are an experienced developer you are probably at the point of needing help from this forum or a consultant to get your site back to a working 2.5 environment. Good luck, it's not fun having a website with a broken 3.x migration and all those DB errors showing on your website! Also consider a new ISP if they don't have their own backup procedures.

Hope this helps!
Joomla! Web Hosting, Design, and Consulting.
Portfolio: http://www.calweb.com/joomla
Please do not PM me for help, use the forums first.

mikerotec
Joomla! Enthusiast
Joomla! Enthusiast
Posts: 170
Joined: Fri Aug 08, 2014 10:08 pm

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by mikerotec » Fri Aug 08, 2014 10:18 pm

humvee wrote: Two very simple solutions to the problems you caused.

[list=1]
[*]Create a backup of the site and database BEFORE any update, Extensions installation or edits of ACL and core code (last not recommended at all).
[*]Don't upgrade to 3.x until the 3.5 LTS release in two years time unless you are advance adopter, experienced user, or developer![/list]
Two years? Not to overstate the obvious - but officially, Joomla 2.5 is VERY CLOSE to it's EOL!

End of Support for 2.5 December 31, 2014
* ( from http://developer.joomla.org/development-status.html )

Due to that, I am feeling a particular urgency to get the migration to 3.x underway... I do not like to be at the bleeding edge of anything, but I have inherited a rather hefty 2.5 site burdened with (way too many, IMO) various extensions and plugins, and I am not confident that they will all be supporting 2.5 for very long... Not to mention the various security implications?

User avatar
euoceo
Joomla! Guru
Joomla! Guru
Posts: 955
Joined: Fri Sep 12, 2008 2:48 pm
Location: Sacramento
Contact:

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by euoceo » Sat Aug 09, 2014 12:06 am

mikerotec wrote:
humvee wrote: Two very simple solutions to the problems you caused.

[list=1]
[*]Create a backup of the site and database BEFORE any update, Extensions installation or edits of ACL and core code (last not recommended at all).
[*]Don't upgrade to 3.x until the 3.5 LTS release in two years time unless you are advance adopter, experienced user, or developer![/list]
Two years? Not to overstate the obvious - but officially, Joomla 2.5 is VERY CLOSE to it's EOL!?
You are quoting a post that is almost 2 years old, so at the time he was entirely correct!
Joomla! Web Hosting, Design, and Consulting.
Portfolio: http://www.calweb.com/joomla
Please do not PM me for help, use the forums first.

mikerotec
Joomla! Enthusiast
Joomla! Enthusiast
Posts: 170
Joined: Fri Aug 08, 2014 10:08 pm

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by mikerotec » Sat Aug 09, 2014 1:55 am

Ah... so there really is a 3.5 LTS version coming "any day now"??

And this will also come with a bulletproof "upgrader" from 2.5.x, the current LTS?? (after 2+ years of pain and suffering by the early adopters...) ??? :pop

User avatar
leolam
Joomla! Master
Joomla! Master
Posts: 19485
Joined: Mon Aug 29, 2005 10:17 am
Location: Netherlands/ UK/ S'pore/Jakarta/ North America
Contact:

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by leolam » Sat Aug 09, 2014 3:28 am

Sorry but this is so utterly nonsense what is being posted here. You are posting here in reaction to a 2-year old and long overhauled post. And @ Mikerotec....you joined on August 8nd just to post with what purpose?

For those who want the real story read this about the next big version which is Joomla 3.4 http://developer.joomla.org/news/589-jo ... pdate.html

Also the REAL story as per today: http://developer.joomla.org/news/586-jo ... ategy.html

also

http://developer.joomla.org/news/587-fa ... cycle.html

Cheers

Leo 8)
Joomla's #1 Professional Support Provider:
-> Joomla Professional Support: https://gws-desk.com -
-> Joomla Specialized Hosting Solutions: https://gws-host.com -
-> Joomla Webmaster Services: gws-webmaster.services

mikerotec
Joomla! Enthusiast
Joomla! Enthusiast
Posts: 170
Joined: Fri Aug 08, 2014 10:08 pm

Re: Upgrade to 3.0 disaster but database 2.5 fixed by euoceo

Post by mikerotec » Mon Aug 11, 2014 6:01 pm

Thanks for the links, Leo - that does clarify the situation.

My purpose in joining this forum is to try to get ready for an upgrade of long-established 2.5 site to 3.x. (The main joomla docs are a bit sketchy with regards to how to best accomplish this!) And what I have mostly found on the forum here are various horror-stories about failed 2.5-to-3.x updates, so I became a bit concerned. I'm pleased to see that 3.3 is considered a stable version, so I am going to work through it on my DEV server in the coming weeks, and hope for the best.


Locked

Return to “Migrating and Upgrading to Joomla! 3.x”