Forums

Covering OroCommerce, OroCRM, OroPlatform topics, including community updates and company announcements.

This topic contains 4 replies, has 2 voices, and was last updated by Andrey Yatsenko Andrey Yatsenko 1 day, 20 hours ago.

  • Creator
    Topic
  • #38058

    Mauro Chojrin
    Participant

    Hi:

    I’m running oroCommerce 1.6 and I’m looking into upgrading to 3.1.

    In the upgrade instructions found here I can see pointers for upgrading minor versions… is there some documentation about how to perform this kind of upgrade?

    Thanks

Viewing 4 replies - 1 through 4 (of 4 total)
  • Author
    Replies
  • #38095
    Andrey Yatsenko
    Andrey Yatsenko
    Moderator

    Hi Mauro,

    The basic steps are the same and you could follow the above instruction. The only important thing that doesn’t mention there that you must read CHANGELOG.md files to see what was changed between 1.6 and 3.1 versions in all the packages you are using and fix your code that depends on that changes before running the standard platform update procedure.

    You can use the following command to find all CHANGELOG.md files in Oro packages:

    The most important change is the Symfony framework upgrade from 2.8 LTS to 3.4 LTS, and to fix first Symfony related issues you should follow the official guide to make your code deprecation free BEFORE upgrading to the 3.1 version.

    #38096

    Mauro Chojrin
    Participant

    Thanks Andrey! I’ll give it a try and report :)

    #38148

    Mauro Chojrin
    Participant

    Ok so I’ve been going around with an upgrade from 1.6 to 3.1 and I had some issues.

    First of all, I wanted to try the upgrade on a VM before I run it in prod and so far, it’s been challenging.

    First I had a few issues with git. When I pulled the changes into my working copy I got a lot of conflicts to be resolved (Outside of my src directory).

    The I had to make a couple of changes to the Nginx configuration… It took a few tries but it seems to be working now.

    There’s one thing in the upgrade documentation that can cause trouble though: it says to run composer update instead of composer install which is not really a good idea :p.

    Is there any other consideration I should have when going into prod?

    Thanks

    #38157
    Andrey Yatsenko
    Andrey Yatsenko
    Moderator

    Good catch, we’ll update the documentation to recommend using composer install, when dependencies are the same as in oro application. Otherwise, it’s required to run composer update.

    Is there any other consideration I should have when going into prod?

    Nothing special, I’ve already described all the required steps.
    It’s recommended to have automated tests for all functionality that you have customized, or at least check it manually after the upgrade.

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

You will be redirected to [title]. Would you like to continue?

Yes No
sso for www.magecore.comsso for oroinc.comsso for oroinc.desso for oroinc.fr