Magento 1.9 Upgrade- Common Problems and Solutions
Time-Saving Integration with Excellent Support
"I like that APPSeCONNECT saves us a lot of time by automating the import of sales orders from Shopify into SAP Business One. It helps in updating business partner contact information, which is great because before we had to hand-type the orders, but now it's all imported smoothly."
Subhajit Goswami3 min readI am sure many of you trying to upgrade your existing Magento Community Website to the newest 1.9 Community Edition. When we want to upgrade we need a proper planning and also it will be really helpful if we know prior, the common problems/mistakes that we do/face during upgrade so that we can take precautions. Through this blog article ‘Magento 1.9 Upgrade- Common Problems and Solutions’ I have tried to gather all the reported problems and solutions which are posted in Magento Forum.
Upgrade Problem from 1.4 to 1.9
Error in file: “/home/www/bastaflora.cz/www/test.bastaflora.cz/app/code/core/Mage/
Core/sql/core_setup/
mysql4-upgrade-1.5.9.9-1.6.0.0.php” – SQLSTATE[HY000]: General error: 1025 Error
on rename of ‘./bastafloracz03/core_url_rewrite’to ‘./bastafloracz03/#sql2-1084-2bad7b’ (errno: 152)
Trace:
#0 /home/www/bastaflora.cz/www/test.bastaflora.cz/app/code/core/Mage/Core/Model/
Resource/Setup.php(645): Mage::exception(‘Mage_Core’, ‘Error in file: …’)
#1 /home/www/bastaflora.cz/www/test.bastaflora.cz/app/code/core/Mage/Core/Model/
Resource/Setup.php(437): Mage_Core_Model_Resource_Setup->_modifyResourceDb
(‘upgrade’, ‘0.8.28’, ‘1.6.0.4’)
#2 /home/www/bastaflora.cz/www/test.bastaflora.cz/app/code/core/Mage/Core/Model/
Resource/Setup.php(320): Mage_Core_Model_Resource_Setup->_upgradeResourceDb(‘0.8.28’, ‘1.6.0.4’)
#3 /home/www/bastaflora.cz/www/test.bastaflora.cz/app/code/core/Mage/Core/Model/
Resource/Setup.php(235): Mage_Core_Model_Resource_Setup->applyUpdates()
#4 /home/www/bastaflora.cz/www/test.bastaflora.cz/app/code/core/Mage/Core/Model/
App.php(417): Mage_Core_Model_Resource_Setup::applyAllUpdates()
#5 /home/www/bastaflora.cz/www/test.bastaflora.cz/app/code/core/Mage/Core/Model/
App.php(343): Mage_Core_Model_App->_initModules()
#6 /home/www/bastaflora.cz/www/test.bastaflora.cz/app/Mage.php(684): Mage_Core_
Model_App->run(Array)
#7 /home/www/bastaflora.cz/www/test.bastaflora.cz/index.php(87): Mage::run(”, ‘store’)
#8 {main}
Solution Given:
- Do the upgrade on replica/test site
- Revert the test/replica site back to default theme
- Do the upgrade in steps, first upgrade from 1.4 to a vanilla 1.6 and then
upgrade 1.6 to 1.9
System Configuration- Blank White Page after upgrade to 1.9.0.1
Upgraded Magento to 1.9.0.1, when I login to the backend of the site the system
configuration page just shows blank.
Solution Given:
Remove all files except config.xml from the following path: /app/code/core/Mage/
GoogleCheckout/etc
Problems in WYSIWYG Editor- Not Saving Links
Upgraded to latest 1.9 but having problems with the WYSIWYG Editor which is not
saving links on the page. When I add a picture and link it to another page, the link
doesn’t get saved.
I have cleared cache, logged out/in etc. without any luck.
Workaround Given:
Disable the editor and post the links using HTML, then again you can enable the WYSIWYG
Editor
Footer link block not visible on RWD_Default responsive theme
I just made an upgrade to Magento 1.9.0.1 and it was working fine but when I change to
theme RWD_Default responsive theme, my footer link block is gone in footer.
Solution Given:
- On the new template rwd_deafult, they have a new block for Company.
- Create a new block to footer and name it like this
Footer Links Company
footer_links_company
Fatal error: Call to a member function getFallbackScheme()
After upgrade from 1.7.x to 1.9.x I get the following error.
Fatal error: Call to a member function getFallbackScheme() on a non-object in \path\to\magento\app\code\core\Mage\Core\Model\Design\Package.php on line 447
Call Stack
# Time Memory Function Location
1 0.0005 260888 {main}( ) ..\index.php:0
2 0.0040 556952 Mage::run( ) ..\index.php:87
3 0.0134 1588376 Mage_Core_Model_App->run( ) ..\Mage.php:684
4 1.9193 10152944 Mage_Core_Controller_Varien_Front->dispatch( ) ..\App.php:354
5 1.9250 10448624 Mage_Core_Controller_Varien_Router_Standard->match( ) ..\Front.php:172
6 1.9313 10984432 Mage_Core_Controller_Varien_Action->dispatch( ) ..\Standard.php:250
7 1.9313 10985008 Mage_Core_Controller_Front_Action->preDispatch( ) ..\Action.php:407
8 1.9347 11273192 Mage_Core_Controller_Varien_Action->preDispatch( ) ..\Action.php:64
9 1.9386 11387536 Mage_Core_Model_App->loadArea( ) ..\Action.php:512
10 1.9386 11387864 Mage_Core_Model_App_Area->load( ) ..\App.php:774
11 1.9445 11809080 Mage_Core_Model_App_Area->_loadPart( ) ..\Area.php:93
12 1.9445 11809080 Mage_Core_Model_App_Area->_initTranslate( ) ..\Area.php:121
13 1.9459 11929296 Mage_Core_Model_Translate->init( ) ..\Area.php:146
14 2.1086 14626416 Mage_Core_Model_Translate->_loadThemeTranslation( ) ..\Translate.php:141
15 2.1086 14626576 Mage_Core_Model_Design_Package->getLocaleFileName( ) ..\Translate.php:277
16 2.1086 14626984 Mage_Core_Model_Design_Package->getFilename( ) ..\Package.php:472
Solution Given:
Possibly the error generated because of some extension.
- Disable All your extensions and check if you are getting this error
- Enable existing extensions one by one and keep checking if you are getting
this error - Identify the extension which causing this error, probably that extension
version is incompatible with Magento 1.9
You may also like:
Time-Saving Integration with Excellent Support
"I like that APPSeCONNECT saves us a lot of time by automating the import of sales orders from Shopify into SAP Business One. It helps in updating business partner contact information, which is great because before we had to hand-type the orders, but now it's all imported smoothly."
Request for a personalized demo
