Updating from 5.5 to current 5.6

Permalink
Folks, as they say "Houston I have a problem". I have tried to update my 5.5 version to the current 5.6 version and get the following error.
An Unexpected Error occurred while upgrading: #0 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/libraries/3rdparty/adodb/adodb.inc.php(641): adodb_throw('mysqlt', 'DOQUOTE', -9999, 'Numeric field t...', '', false, Object(ADODB_mysqlt)) #1 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/core/libraries/model.php(44): ADOConnection->outp_throw('Numeric field t...', 'DOQUOTE') #2 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/libraries/3rdparty/adodb/adodb-active-record.inc.php(845): Concrete5_Library_Model->doquote(Object(ADODB_mysqlt), true, 'I') #3 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/core/models/block_types.php(763): ADODB_Active_Record->Replace() #4 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/core/models/block_types.php(671): Concrete5_Model_BlockType->doInstallBlockType('core_scrapbook_...', Object(BlockType), '/websites/pa/pa...', '1', '/websites/pa/pa...') #5 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/core/models/block_types.php(632): Concrete5_Model_BlockType->installBlockType('core_scrapbook_...', '1') #6 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/helpers/concrete/upgrade/version_560.php(102): Concrete5_Model_BlockType->refresh() #7 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/core/controllers/single_pages/upgrade.php(272): ConcreteUpgradeVersion560Helper->run() #8 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/core/controllers/single_pages/upgrade.php(44): Concrete5_Controller_Upgrade->do_upgrade() #9 [internal function]: Concrete5_Controller_Upgrade->view('tools', 'required', 'upgrade') #10 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/core/libraries/controller.php(267): call_user_func_array(Array, Array) #11 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/core/libraries/controller.php(237): Concrete5_Library_Controller->runTask('view', Array) #12 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/core/libraries/view.php(787): Concrete5_Library_Controller->setupAndRun() #13 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/tools/upgrade.php(6): Concrete5_Library_View->render('/upgrade') #14 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/startup/tools_upgrade_check.php(9): include('/websites/pa/pa...') #15 /websites/pa/paces.com.au/concrete5/updates/concrete5.6.3.2/concrete/dispatcher.php(105): require('/websites/pa/pa...') #16 /websites/pa/paces.com.au/concrete5/concrete/startup/updated_core_check.php(6): require('/websites/pa/pa...') #17 /websites/pa/paces.com.au/concrete5/concrete/dispatcher.php(20): require('/websites/pa/pa...') #18 /websites/pa/paces.com.au/concrete5/index.php(2): require('/websites/pa/pa...') #19 {main}

Is this a concrete5 problem or is it a Host Server problem. If server problem, what do I need to have done by my hosting people - MelbourneIT

Thanks for any suggestions or help

Globetrotter101
 
Globetrotter101 replied on at Permalink Reply
Globetrotter101
Bump - anyone got ideas on why this happens
mesuva replied on at Permalink Reply
mesuva
I think you've hit a bug that has been fixed in github, but not in the latest 5.6 release.

It's referenced here:
https://www.concrete5.org/developers/bugs/5-6-3-1/upgrade-from-5.5.2...

It does look like a pretty easy fix though, it's a single liner. Hissy worked it out here:
https://github.com/hissy/concrete5/commit/407a392ed90bf9774020c53838...

Try adding that line in green to /concrete/helpers/concrete/upgrade/version_560.php and repeating the upgrade process.
Globetrotter101 replied on at Permalink Reply
Globetrotter101
Thanks for that Mesuva, will give it a try later today
Globetrotter101 replied on at Permalink Reply
Globetrotter101
Many many thanks Mesuva for that. That simple change made the update work - I am now up to 5.6.0.0 and currently no errors
ProjbyP replied on at Permalink Reply
ProjbyP
I am having the same problem - a client didn't update for too long and now the update fails with similar errors.

I was hoping I could upgrade with legacy versions in steps, i.e., 5.6.0, 5.6.1, 5.6.2, etc. but can't proceed. I thought if I added the zip files to the update folder, the system would find the newer versions, but alas it does not work! It's looking for the last version, which produces the errors and site goes poof!