ssossossosso

Forums

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

This topic contains 3 replies, has 3 voices, and was last updated by  andesk 2 years, 12 months ago.

  • Creator
    Topic
  • #5176

    hemham914
    Participant

    Hello. I am getting this error after updating composer and running a fresh install on oro. Cleared the cache too:

    Any ideas?


    ~Coding my life away~

Viewing 3 replies - 1 through 3 (of 3 total)
  • Author
    Replies
  • #5181

    Alexandr Smaga
    Participant

    Hello.

    This issue appeared due to changes in knpmenu bundle. But version that we depends on is “knplabs/knp-menu”: “2.0.0-alpha2” and it should not contain this commit, see. So it looks like you have another version of this bundle.

    #5189

    andesk
    Participant

    Hi there!

    When using OroPlatform 1.2 the version requirements are set to 2.0.0-alpha2 in composer.json. They are not for previous versions of OroPlatform (1.1.1 and before) though:

    What you can do to get those applications to work properly (without updating OroPlatform) is to add following lines to your own composer.json:

    See also: https://getcomposer.org/doc/articles/aliases.md#require-inline-alias

    Be aware, that when updating OroPlatform, you have to remove those lines again, as otherwise requirements can not be resolved.

    #5190

    andesk
    Participant

    Hm.

    Just checked: the version requirements are wrong in Platform 1.2.0 as well (2.0.x-dev instead of 2.0.0-alpha2): https://github.com/orocrm/platform/blob/1.2.0/composer.json

    They are fixed in master though: https://github.com/orocrm/platform/blob/master/composer.json

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

You must be logged in to reply to this topic.