OroCRM Forums

Covering OroCRM topics, including community updates and company announcements.

This topic contains 8 replies, has 2 voices, and was last updated by  Mauro Chojrin 3 months, 3 weeks 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 8 replies - 1 through 8 (of 8 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.

    #38177

    Mauro Chojrin
    Participant

    Hi Andrey:

    Here I am reporting back :).

    I just finished updating my production environment to 3.1 and it seems to be working fine (I’ll keep posting here if I find any issue).

    A couple of things that might be helpful to others attempting this:

    1 – Watch out for the new configuration of Nginx (Directories and other things changed between 1.6 and 3.1, have a look at https://oroinc.com/b2b-ecommerce/doc/current/install-upgrade/installation-quick-start-dev/commerce-crm#configure-web-server in case of need).
    2 – Same goes for supervisord config (Check your /etc/supervisord.conf file).

    I had to also upgrade my php (I had version 7.1.25 and oroCommerce required 7.1.26… no big deal, but I had to do it.

    Just to make the scenario complete (And related to my other posts), the way I’m handling the code is:

    I have a private repo to which I push (and from where I pull in my prod environment) and I pull the changes from oro’s github in my dev machine (from where I push to my private repo).

    I did this since I had to create an integration and I wanted to keep my code versioned as well.

    Thanks and I hope this helps :)

    #38190

    Mauro Chojrin
    Participant

    Another thing I just noticed:

    The images I had uploaded were missing… I got them back by copying the directory
    web/media/cache/attachment from my backup into public/media/cache/attachment of my webroot

    #38331

    Mauro Chojrin
    Participant

    Just picked up on another little detail. Going from 1.6 to 3.1 the server used to process websockets changed from clank to gos, so an additional configuration change is the update to /etc/supervisord.conf from:

    to:

    #38421

    Mauro Chojrin
    Participant

    Another thing to be careful with: the cronjob will no longer work since the console command now lives at

    oroapp/bin/console

    , so instead of

    */1 * * * * php /usr/share/nginx/html/oroapp/app/console oro:cron --env=prod > /dev/null

    it should read

    */1 * * * * php /usr/share/nginx/html/oroapp/bin/console oro:cron --env=prod > /dev/null
Viewing 8 replies - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.

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

Yes No