3

I was reading the upgrade guide - but had the idea to try the upgrade via Magento connect. THis has always worked before ;P

http://www.magentocommerce.com/knowledge-base/entry/ce18-upgrade-roadmap

Is there a real reason why we should not upgrade via Magento Connect in backend?

2

If you have no any third party or local extensions that store theirs templates and layout files in app\design\frontend\base\default everything should be ok.

I am not sure but during updating Mage_Core_Modules magento should delete everything what is inside app\design\frontend\base\default and copy new version files there.

So double check that.

  • Delete all like in .? Or does it delete the new files it will later save in app\design\frontend\base\default – snh_nl Mar 27 '14 at 12:52
2

We ended up upgrading our whole store using Magento connect

We did encounter missing some JS files, but after fixing that we were fine

http://www.magentocommerce.com/boards/viewthread/664565/

Magento 1.8.1 quick create no longer working JS error

It is still th easiest way

  • I did it this way and worked fine but avoid the temptation to just switch the js folder old for new like I did - the js folder is used for extensions. In the end I just added the scripaculuous folder to it from the official 1.8 version. – byronyasgur Apr 18 '14 at 14:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.