cancel
Showing results for 
Search instead for 
Did you mean: 

2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

System is Ubuntu 18.04, PHP 7.2.16 running Magento 2.3.0 perfectly

Why is the upgrade telling me I have the wrong PHP version?

 

root@master:/home/{redacted}/domains/staging.{redacted}.com/public_html# composer require magento/product-community-edition=2.3.1 --no-update
./composer.json has been updated
root@master:/home/{redacted}/domains/staging.{redacted}.com/public_html# composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

Problem 1
- magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0 -> your PHP version (7.2.16) does not satisfy that requirement.
13 REPLIES 13

Re: 2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

Best,

 

Same issue here, i can not find any solutions yet.

Re: 2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

The 100.2.8 version is tied to Magento 2.2.8

Magento 2.3.1 should be loading version 101.0.1 which has "php": "~7.1.3||~7.2.0" requirement

See

https://github.com/magento/magento2/blob/2.2.8/app/code/Magento/Backend/composer.json

Vs.

https://github.com/magento/magento2/blob/2.3.1/app/code/Magento/Backend/composer.json

If you've found one of my answers useful, please give "Kudos" or "Accept as Solution"

Re: 2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

Best,

 

Thanks fo the reply but my installation does not have such Path:

/app/code/Magento/Backend/composer.json

 

Where to find the right composer.json file?

I believe it is somewhere in /Vendor But i don't know where to look.

 

Thanks

 

Re: 2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

Your code won't be there are you've installed the system with composer. It should be at vendor/magento/module-backend/composer.json as your installation failed though it may not be.

 

What does your composer.json look like in the Magento directory after running

composer require magento/product-community-edition=2.3.1 --no-update
If you've found one of my answers useful, please give "Kudos" or "Accept as Solution"

Re: 2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

After running, in my root folder

composer require magento/product-community-edition=2.3.1 --no-update

composer.json in the same folder has no reference to module-backend and appears in full like this:

{
    "name": "magento/project-community-edition",
    "description": "eCommerce Platform for Growth (Community Edition)",
    "type": "project",
    "version": "2.1.3",
    "license": [
        "OSL-3.0",
        "AFL-3.0"
    ],
    "require": {
        "magento/product-community-edition": "2.3.1",
        "composer/composer": "@alpha",
        "fooman/pdfcustomiser-m2": "^8.1",
        "coingate/magento2-plugin": "^1.0",
        "magepal/magento2-gmailsmtpapp": "2.6.0",
        "flancer32/mage2_ext_free_rates": "^0.1.0",
        "thanhdv2811/magento-2-currency-convert": "^1.0"
    },
    "require-dev": {
        "phpunit/phpunit": "~6.2.0",
        "squizlabs/php_codesniffer": "3.2.2",
        "phpmd/phpmd": "@stable",
        "pdepend/pdepend": "2.5.2",
        "lusitanian/oauth": "~0.8.10",
        "sebastian/phpcpd": "~3.0.0",
        "friendsofphp/php-cs-fixer": "~2.10.1"
    },
    "config": {
        "use-include-path": true
    },
    "autoload": {
    "psr-4": {
        "Magento\\Framework\\": "lib/internal/Magento/Framework/",
        "Magento\\Setup\\": "setup/src/Magento/Setup/",
        "Magento\\": "app/code/Magento/",
        "Zend\\Mvc\\Controller\\": "setup/src/Zend/Mvc/Controller/"
    },
        "psr-0": {
            "": "app/code/"
        },
        "files": [
            "app/etc/NonComposerComponentRegistration.php"
        ]
    },
    "autoload-dev": {
        "psr-4": {
            "Magento\\Sniffs\\": "dev/tests/static/framework/Magento/Sniffs/",
            "Magento\\Tools\\": "dev/tools/Magento/Tools/",
            "Magento\\Tools\\Sanity\\": "dev/build/publication/sanity/Magento/Tools/Sanity/",
            "Magento\\TestFramework\\Inspection\\": "dev/tests/static/framework/Magento/TestFramework/Inspection/",
            "Magento\\TestFramework\\Utility\\": "dev/tests/static/framework/Magento/TestFramework/Utility/"
        }
    },
    "minimum-stability": "alpha",
    "prefer-stable": true,
    "repositories": {
        "0": {
            "type": "composer",
            "url": "https://repo.magento.com/"
        },
        "fooman": {
            "type": "composer",
            "url": "https://customer-repos.fooman.co.nz/{redacted}"
        }
    },
    "extra": {
        "magento-force": "override"
    }
}

The composer.json from vendor/magento/module-backend is  the same as your linke, which says it can't handle php later than 7.2.0. Surely this is the problem here, and a mistake on their part? "Magento 2.3.1 is certified for PHP 7.2.11":  https://devdocs.magento.com/guides/v2.3/install-gde/system-requirements-tech.html 

 

{
    "name": "magento/module-backend",
    "description": "N/A",
    "config": {
        "sort-packages": true
    },
    "require": {
        "php": "~7.1.3||~7.2.0",
        "magento/framework": "102.0.*",
        "magento/module-backup": "100.3.*",
        "magento/module-catalog": "103.0.*",
        "magento/module-config": "101.1.*",
        "magento/module-customer": "102.0.*",
        "magento/module-developer": "100.3.*",
        "magento/module-directory": "100.3.*",
        "magento/module-eav": "102.0.*",
        "magento/module-quote": "101.1.*",
        "magento/module-reports": "100.3.*",
        "magento/module-require-js": "100.3.*",
        "magento/module-sales": "102.0.*",
        "magento/module-security": "100.3.*",
        "magento/module-store": "101.0.*",
        "magento/module-translation": "100.3.*",
        "magento/module-ui": "101.1.*",
        "magento/module-user": "101.1.*"
    },
    "suggest": {
        "magento/module-theme": "101.0.*"
    },
    "type": "magento2-module",
    "license": [
        "OSL-3.0",
        "AFL-3.0"
    ],
    "autoload": {
        "files": [
            "registration.php"
        ],
        "psr-4": {
            "Magento\\Backend\\": ""
        }
    },
    "version": "101.0.0"
}

 

Re: 2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

I suggest you redact the fooman link as it is confidential to you

If you've found one of my answers useful, please give "Kudos" or "Accept as Solution"

Re: 2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

My solution.

 

I downloaded the magento 2.3.1 instance.

Renamed my composer.json file to composer.json.old

Copied the file composer.json from the fresh magento 2.3.1 to my 2.3.0

 

I do nut understand your fooman answer.

 

Problem solved.

 

 

Re: 2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

I have a solution that worked for me

My solution.

 

I downloaded the magento 2.3.1 instance.

Renamed my composer.json file to composer.json.old

Copied the file composer.json from the fresh magento 2.3.1 to my 2.3.0

 

Problem solved.

 

 

Re: 2.3.0 to 2.3.1: magento/module-backend 100.2.8 requires php ~7.0.13|~7.1.0

In you composer.json file posted earlier remove everything after

https://customer-repos.fooman.co.nz/

as it contains information that would allow other people to use your paid for modules

 

Glad you got it working!

If you've found one of my answers useful, please give "Kudos" or "Accept as Solution"