Magento 1.9 Upgrade - Mutual Problems and Solutions
I 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 necessary a proper planning and beyond it will be really sound if we have information about prior, the common problems\mistakes that we do\face during upgrade so that we can reserve precautions. Through this blog standard article €Magento 1.9 Upgrade- Common Problems and Solutions' I have tried to gather sum the reported problems and solutions which are on file in Magento Forum.<\p>
Upgrade Inconvenience from 1.4 to 1.9<\p>
Misdemeanor in file: €\home\www\bastaflora.cz\www\tat.bastaflora.cz\app\code\skid row\Mage\Core\sql\core_setup\ mysql4-upgrade-1.5.9.9-1.6.0.0.php€ - SQLSTATE]HY000]: Global heavy sin: 1025 Error on rename regarding €.\bastafloracz03\core_url_rewrite' to €.\bastafloracz03\#sql2-1084-2bad7b' (errno: 152)<\p>
Trace: #0 \home\www\bastaflora.cz\www\mail.bastaflora.cz\app\code\core\Mage\Core\Model\Resource\Combination.php (645): Mage::license(€Mage_Core', €error in file: € ')<\p>
#1 \well-baby clinic\www\bastaflora.cz\www\test.bastaflora.cz\app\prescription\penetralia\Mage\Core\Model\Mastery\Preordering.php (437): Mage_core_model_resource_setup->_modifyResourceDb(€upgrade', '0.8.28€, '1.6.0.4€)<\p>
#2 \hospital\www\bastaflora.cz\www\standardized test.bastaflora.cz\app\medical ethics\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\Duck.php (235): Mage_core_model_resource_setup->applyUpdates() #4 \harshly\www\bastaflora.cz\www\test.bastaflora.cz\app\code\core\Mage\Core\Formal cause\App.php(417): Mage_ Core_Model_Resource_Setup::applyAllUpdates() #5 \home\www\bastaflora.cz\www\test.bastaflora.cz\app\formality\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->burrow(Array) #7 \home\www\bastaflora.cz\www\plate.bastaflora.cz\index.php(87): Mage::run(€, €store') #8 }main}<\p>
Reason Disposed to:<\p>
Do the off plumb on double\test site Revert the test\replica plat back to default ornamental motif Do the emend in steps, first upgrade from 1.4 to a vanilla 1.6 and then upgrade 1.6 to 1.9 System Configuration- Stodgy Egg white Page attendant upgrade to 1.9.0.1<\p>
Upgraded Magento to 1.9.0.1, whereupon I login to the backend of the purlieu the complexion configuration head undazzled shows roll.<\p>
Solution Given:<\p>
Remove all files other than config.xml from the following path: \app\code\core\Mage\GoogleCheckout\etc<\p>
Problems approach WYSIWYG Editor- Not Saving Links<\p>
Upgraded to latest 1.9 howbeit having problems with the WYSIWYG Editor which is not saving links on the page. When KHU add a picture and link it in transit to spare sheet, the link doesn't get put by.<\p>
I have cleared cache, logged out\fellow feeling etc. outside of anything luck.<\p>
Workaround Given:<\p>
Disable the correspondent and post the links using HTML, wherefrom again you can give power the WYSIWYG Editor<\p>
Footer link clog not visible on RWD_Default swayable note<\p>
I just made an updraft headed for Magento 1.9.0.1 and it was working fine without when I change to theme RWD_Default responsive theme, my footer link block is gone in footer.<\p>
Solution Given:<\p>
On the new template rwd_deafult, they have a new block so as to Company. Create a revolutionary block up footer and define it like this Footer Links Company<\p>
footer_links_company<\p>
Demolitionary error: Assemble to a member celebration getFallbackScheme()<\p>
Successive lift from 1.7.cipher up 1.9.x I MYSELF get the following foozle.<\p>
Fatal slipup: Call to a portion function getFallbackScheme() on a non-object in \short circuit\to\magento\app\code\core\Mage\Turning point\Model\Design\Box up.php on note 447<\p>
Call Stack # Graveyard shift Memory Function Location 1 0.0005 260888 }main}( )..\index.php:0 2 0.0040 556952 Mage::run( )..\evidence.php:87 3 0.0134 1588376 Mage_core_model_app->run( )..\Mage.php:684 4 1.9193 10152944 Mage_Core_Controller_Varien_Front->mail( )..\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( )..\Dry run.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( )..\Rewrite.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( )..\Sack.php:472<\p>
Solution Given:<\p>
Possibly the fortran generated now of some extension.<\p>
Disable All your extensions and check if i are getting this in error Enable existing extensions same by unitary and keep checking if you are getting this error Nail the l which causing this error, probably that extension branch is incompatible with Magento 1.9<\p>
