ssossossosso

Forums

Covering OroCRM topics, including community updates and company announcements.  Subscribe

This topic contains 7 replies, has 3 voices, and was last updated by Vladyslav Byndych Vladyslav Byndych 5 days, 2 hours ago.

  • Creator
    Topic
  • #37666
    Anton
    Anton
    Participant

    Application Type: OroCRM
    Application Edition: Community

    php version: 7.0.15
    mysql version: 5.6.34-79.1
    nginx version: nginx/1.11.10
    CentOS Linux release 7.3.1611 (Core)

    Issue: Upgrading from 1.10 to 2.0

    Is it possible to immediately upgrade orocrm from version 1.10 to 2.0?

    When the platform upgrade (the command php app/console oro: platform:update –env=prod –force) shows this error: Fatal error: Uncaught Error: Class ‘OroCRM \ Bundle \ ZendeskBundle \ OroCRMZendeskBundle’ not found in / home /WEBSITE/dev/mgrcrm/app/cache/prod/bundles.php:110 Stack trace: # 0 /home/WEBSITE/dev/mgrcrm/vendor/oro/platform/src/Oro/Bundle/DistributionBundle/OroKernel.php ( 75): require () # 1 /home/WEBSITE/dev/mgrcrm/app/AppKernel.php(27): Oro \ Bundle \ DistributionBundle \ OroKernel-> registerBundles () # 2 / home / WEBSITE / dev / mgrcrm / app /bootstrap.php.cache(2673): AppKernel-> registerBundles () # 3 /home/WEBSITE/dev/mgrcrm/vendor/oro/platform/src/Oro/Bundle/DistributionBundle/OroKernel.php(34): Symfony \ Component \ HttpKernel \ kernel-> initializeBundles () # 4 /home/WEBSITE/dev/mgrcrm/app/bootstrap.php.cache(2502): Oro \ Bundle \ DistributionBundle \ OroKernel-> initializeBundles () # 5 / home / WEBSITE / Dev / mgrcrm / vendor / o ro / platform / src / Oro / Bundle / DistributionBundle / OroKernel.php (250): Symfony \ Component \ HttpKernel \ Kernel-> boot () # 6 /home/WEBSITE/dev/mgrcrm/app/bootstrap.php.cache ( 2534): Oro \ Bundle \ DistributionBundle \ OroKernel-> boot () # 7 / home / volta in /home/WEBSITE/dev/mgrcrm/app/cache/prod/bundles.php on line 110

    We are trying to update to version 1.10.10. Previously, we tried to immediately upgrade to version 2.0, then there were a lot of errors. We updated the version of the OROCRM which was previously installed on the dev site, but it did not seem to contain some files for which the configuration was specified in the database. Then we replaced the version of the OROCRM on the dev site with the version of the live site and the database, respectively. And we began to update gradually, at least to version 1.10.10. But there was the specified error.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Author
    Replies
  • #37669

    Hi Anton,

    Yes, direct upgrade form 1.10.0 to 2.0 is available but procedure is slightly different then described in

    How to Upgrade to a New Version

    Instead of

    you should use

    This is happened due to big namespace changes which were introduced in 2.0, so please read more details about that changed here:
    https://github.com/oroinc/platform/blob/master/UPGRADE-2.0.md
    https://github.com/oroinc/crm/blob/master/UPGRADE-2.0.md

    #37857
    Anton
    Anton
    Participant

    Hi Vlad,

    Thank you for the reply.

    Unfortunately, we are still getting errors we can’t figure out. Please see the following screenshot:

    http://prntscr.com/gg4438

    What should we do?

    • This reply was modified 2 weeks, 5 days ago by Anton Anton.
    #39129
    Anton
    Anton
    Participant

    Any ideas? We have been stuck for a few weeks now not able to update.

    #39186
    Anton
    Anton
    Participant

    Bump

    #39210

    Hi Anton,

    Could you post file composer.lock of your application ?

    #39215
    Anton
    Anton
    Participant
    #39217

    Hi Anton,

    As I can see from your composer.lock file you getting such error because CRM and Platform code version is 1.10 but upgrade20 command was added in 2.0 version specially for upgrade. So my suggestion is to ensure the CRM and Platform code is 2.0 before run the command.

    To do this you should checkout to 2.0.21 tag if you are using GIT to clone OROCRM application code or download archive with source code here and unpack it to the target folder.

    When you’ve done with it and your composer.lock file is up-to-date, please run composer install command to receive all dependencies. Also don’t forget to cleanup caches and do DB backup. Commands and more details for all described steps can be found on How to Upgrade to a New Version page.

    Finally after all this preparations you should be ready to run:

    Please let me know if still have any questions.

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

You must be logged in to reply to this topic.