composer.json is locked to Commerce 2 and D11 needs Commerce 3

Issue fork commerce_klarna_payments-3506060

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

intrafusion created an issue. See original summary.

intrafusion opened merge request !12

intrafusion’s picture

intrafusion
Primary language English
Location Edinburgh, UK
commented
Status: Active » Needs review
tuutti’s picture

tuutti commented

Hi!

Did you test if this works out of the box with Commerce 3? I'm super busy at the moment and won't have time to test this myself

intrafusion’s picture

intrafusion
Primary language English
Location Edinburgh, UK
commented

At this stage I needed this patch to be able to install Drupal 11.

It will be tested further during the next few weeks.

trickfun’s picture

trickfun commented

I can't install Commerce 3
Patch is installed but i can't update to 3 version.
Thank you

intrafusion’s picture

intrafusion
Primary language English
Location Edinburgh, UK
commented

@trickfun the patch on it's own is not enough to upgrade, your repositories section of composer.json it should look like:

    "repositories": [
        {
            "type": "composer",
            "url": "https://packages.drupal.org/8",
            "exclude": [
                "drupal/commerce_klarna_payments"
            ]
        },
        {
            "type": "git",
            "url": "https://git.drupalcode.org/issue/commerce_klarna_payments-3506060.git"
        }
    ],

You may have additional repositories so ensure you don't override something else you need. You should then be able to run composer require drupal/commerce_klarna_payments:dev-3506060-support-commerce-3 to install the patched version allowing the upgrade.

tuutti’s picture

tuutti commented

You can also try https://github.com/mglaman/composer-drupal-lenient

intrafusion’s picture

intrafusion
Primary language English
Location Edinburgh, UK
commented
Status: Needs review » Reviewed & tested by the community

As per my comment in #5, this has been running for a few weeks on our production system and appears to be working as expected

tuutti’s picture

tuutti commented
Status: Reviewed & tested by the community » Fixed

Thanks! This should be fixed in beta5 release

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.