1

In the release-notes they say

You currently cannot upgrade to this version using Magento Connect Manager. We expect to resolve this issue soon.

How am I supposed to update my production system, which runs on 1.9.2.4?

I tried replacing core and community directories in the app folder. But that resulted in an error.

4

Yikes.

Don't update a production site directly in production. You WILL have a production site that is broken and endless days of stress that is totally avoidable.

Do it right.

Get a dev site up. Upgrade there. Test every aspect of your site after the upgrade.

You WILL need to upgrade most 3rd party extensions. You WILL need to re-integrate your custom templates.

Once you are done, you can deploy to production.

Upgrades are fairly complex. There is no magic GO button.

It is up to you how you setup the dev and test sites. Using docker can make that easy, and not take a lot of your time.

https://github.com/ProxiBlue/vagrant-docker

For the upgrade itself, download the core magento package and drop that into the dev folder version of your site.

Clear cache. ( or better use n98-magerun to effect the upgrade scripts )

Good luck.

(Please, don't do it direct on production, or else we might just see you scream for help on a dead production site next)

  • ok. I'm not very experienced but I updated my dev system successfully. I got this project form someone else. It's a small project. What folders/files do I need to send to the production system now? – Philipp Sander Nov 23 '16 at 15:25
  • 1
    Everything. Best you first backup younlive db. Then make a copy of the folder the live code is on, just a simple file backup of current live code to another folder. Then send all fikes to replace all files from dev to live. Rsync is helpfull here as you can use it to sync with a --size-only switch. Meaning the bulk of the files that is still the same will not transfer over, making the send a lot faster. – ProxiBlue Nov 23 '16 at 15:32
  • 1
    Well. Exclude the media-folder or your product images might be missing – Seb Nov 23 '16 at 15:33
  • Good point. @seb – ProxiBlue Nov 23 '16 at 15:34
  • Highly recommend that you use GIT or SVN to manage the code. Pushing changes from your dev to production is usually as simple as a SSH command to pull in the update code. Even if you don't use GIT on the production code, using a tool such as SourceTree to track your dev code really helps identify which code has been pushed to the server and which hasn't. (EX: login with FTP... copy a modified or new file to production server, add file to GIT repo, commit) – Phil M Nov 24 '16 at 0:49

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.