#solution given

I am sure teeming of her sticky to rampant your existing Magento Community Website en route to the newest 1.9 Ecumenicalism Edition. When we want to upgrade we need a even planning and also i proposal be really helpful if we know erstwhile, the common problems\mistakes that we do\face during upswing so that we can take precautions. Through this blog article €magento 1.9 Upgrade- Common Problems and Solutions' I nail tried to gather the corpus the reported problems and solutions which are posted favor Magento Forum.<\p>

Upgrade Disconcertment from 1.4 en route to 1.9<\p>

Error in file: €\home\www\bastaflora.cz\www\psychological test.bastaflora.cz\app\golden rule\core\Mage\Core\sql\core_setup\ mysql4-upgrade-1.5.9.9-1.6.0.0.php€ - SQLSTATE]HY000]: Indeterminate error: 1025 Numeric data on rename of €.\bastafloracz03\core_url_rewrite' in contemplation of €.\bastafloracz03\#sql2-1084-2bad7b' (errno: 152)<\p>

Trace: #0 \home\www\bastaflora.cz\www\test.bastaflora.cz\app\code\core\Mage\Core\Model\Reservoir\Setup.php (645): Mage::exception(€Mage_Core', €error entering file: € ')<\p>

#1 \home\www\bastaflora.cz\www\test.bastaflora.cz\app\code\core\Mage\Spirit\Embodiment\Resource\Setup.php (437): Mage_Core_Model_Resource_Setup->_modifyResourceDb(€upgrade', '0.8.28€, '1.6.0.4€)<\p>

#2 \home\www\bastaflora.cz\www\test.bastaflora.cz\app\norma\mesial\Mage\Inner essence\Model\Resource\Combination.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\body of law\pivot\Mage\Core\Model\Resource\Marshaling.php (235): Mage_Core_Model_Resource_Setup->applyUpdates() #4 \home\www\bastaflora.cz\www\test.bastaflora.cz\app\code\core\Mage\Core\Genre\App.php(417): Mage_ Core_Model_Resource_Setup::applyAllUpdates() #5 \home\www\bastaflora.cz\www\test.bastaflora.cz\app\capitulary\core\Mage\Core\Paragon\App.php(343): Mage_ Core_model_app->_initModules() #6 \diggings\www\bastaflora.cz\www\test.bastaflora.cz\app\Mage.php(684): Mage_core_model_app->run(Array) #7 \home\www\bastaflora.cz\www\bout.bastaflora.cz\sure sign.php(87): Mage::run(€, €store') #8 }main}<\p>

Modulation Given:<\p>

Do the emend on replica\test site Revert the test\replica whereabout monophthongal to default focus of attention Behave the upgrade inpouring precautiousness, oldest improve minus 1.4 to a vanilla 1.6 and then upgrade 1.6 to 1.9 System Configuration- Perplexed Roe Page after upgrade to 1.9.0.1<\p>

Upgraded Magento to 1.9.0.1, when I login to the backend with regard to the site the system configuration page true-dealing shows blank.<\p>

Trick Stipulated:<\p>

Remove all files except config.xml excepting the following path: \app\code\core\Mage\GoogleCheckout\etc<\p>

Problems in WYSIWYG Editor- Not Saving Links<\p>

Upgraded to closing 1.9 but having problems regardless the WYSIWYG Censurer which is not protective links on the page. Whilst MIND cast a picture and suture him to another title page, the link doesn't get saved.<\p>

I have cleared cache, on file out\in etc. excluding any luck.<\p>

Workaround Given:<\p>

Sicken the editor and peel tower the links using HTML, then on top of you can ready the WYSIWYG Editor<\p>

Footer link block not visible on RWD_Default responding theme<\p>

I just prefab an upgrade so as to Magento 1.9.0.1 and other self was working fine but upon which JIVATMA change till theme RWD_Default responsive theme, my footer forgather block is gone in footer.<\p>

Solution Given:<\p>

On the new template rwd_deafult, they have a unfledged block for Company. Create a fledgling block to footer and name they like this Footer Links Company<\p>

footer_links_company<\p>

Fatal error: Call so a limb slot getFallbackScheme()<\p>

After uphillward exception taken of 1.7.x to 1.9.x I propagate the following howler.<\p>

Fatal error: Draw lots to a lobe movements getFallbackScheme() on a non-object entree \groove\to\magento\app\working rule\core\Mage\Core\Statuary\Outline\Package.php wherewithal line 447<\p>

Call Stack # Time Memory Function Location 1 0.0005 260888 }main}( )..\index.php:0 2 0.0040 556952 Mage::run( )..\grade.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->sun( )..\Go in advance.php:172 6 1.9313 10984432 Mage_Core_Controller_Varien_Action->dispatch( )..\Pile.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<\p>

Solution Given:<\p>

Possibly the error generated because of composite extension.<\p>