cancel
Showing results for 
Search instead for 
Did you mean: 

Errors updating from 2.4.1 to 2.4.4

Errors updating from 2.4.1 to 2.4.4

Hi - I'm trying to update a Magento 2.4.1 site to 2.44 so that I can install the CVE-2024-34102 patch

 

I'm hitting some errors when I run composer update -w after I run composer require-commerce magento/product-community-edition 2.4.4 --no-update

 

These are:

Problem 1 - Root composer.json requires aheadworks/module-affiliate ^1.2, found aheadworks/module-affiliate[1.2.4] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

Problem 2 - Root composer.json requires magento/product-community-edition 2.4.4 -> satisfiable by magento/product-community-edition[2.4.4]. - magento/product-community-edition 2.4.4 requires guzzlehttp/guzzle ^7.3.0 -> found guzzlehttp/guzzle[7.3.0, ..., 7.8.1] but it conflicts with your root composer.json require (^6.5).

Problem 3 - Root composer.json requires magento/magento-coding-standard ~1.0.0 -> satisfiable by magento/magento-coding-standard[1.0.0, 1.0.1, 1.0.2]. - magento/magento-coding-standard[1.0.0, ..., 1.0.2] require squizlabs/php_codesniffer ~3.3.0 -> found squizlabs/php_codesniffer[3.3.0, 3.3.1, 3.3.2] but it conflicts with your root composer.json require (~3.6.0).

Problem 4 - magento/magento2-functional-testing-framework[3.7.0, ..., 3.12.0] require guzzlehttp/guzzle ^7.3.0 -> found guzzlehttp/guzzle[7.3.0, ..., 7.8.1] but it conflicts with your root composer.json require (^6.5). - Root composer.json requires magento/magento2-functional-testing-framework ^3.7 -> satisfiable by magento/magento2-functional-testing-framework[3.7.0, ..., 3.12.0].

 

Any ideas / hacks about how to resolve these errors

3 REPLIES 3

Re: Errors updating from 2.4.1 to 2.4.4

For problems 2-4: Update your composer.json' require versions for those.

 

For 1: Check with AheadWorks from whom you bought that module. Maybe you have to extend your licence to be able to fetch the upgraded version of the module that works with 2.4.4.

 

BTW. If you're already working on an upgrade, why not upgrade all the way to the latest version of Magento? 

Founder at https://agency418.com

Re: Errors updating from 2.4.1 to 2.4.4

@jongreydav8ea3 

 

Hey,

 

Remove : aheadworks/module-affiliate and then execute composer require-commerce magento/product-community-edition 2.4.4 --no-update after successfully upgrading then execute " composer require aheadworks/module-affiliate --ignore-platform-reqs

 

Thank You!

Problem solved? Click Kudos and "Accept as Solution".
200+ Magento 2 Extensions for Enhanced Shopping Experience.

Re: Errors updating from 2.4.1 to 2.4.4

Hello @jongreydav8ea3,

 

To resolve the errors you're encountering when trying to update Magento from 2.4.1 to 2.4.4, there are a few steps and workarounds that may help address the dependency conflicts in your composer.json.

 

Steps to resolve:

  1. Handling aheadworks/module-affiliate:
    • The error suggests that version 1.2.4 is found in the lock file but not available in remote repositories. You can:
      • Check if you have the aheadworks repository added in your composer.json. If not, add the repository URL provided by Aheadworks.
      • Or, as a quick workaround, if you don't need to update this module immediately, you can modify the composer.json to avoid updating this module:
composer update --ignore-platform-reqs aheadworks/module-affiliate

 

Conflict with guzzlehttp/guzzle:

  • The guzzlehttp/guzzle conflict arises because Magento 2.4.4 requires guzzle 7.x, but your root composer.json requires ^6.5. To resolve this:
    • Update the guzzlehttp/guzzle requirement in your composer.json to ^7.3:

"guzzlehttp/guzzle": "^7.3"

 

After updating the requirement, run:

composer update guzzlehttp/guzzle --with-dependencies

  • Make sure there are no other packages in your project that explicitly require Guzzle 6.5. If there are, consider upgrading those packages or finding alternatives.

 

PHP_CodeSniffer version conflict:

  • The Magento coding standards package requires php_codesniffer ~3.3.0, but your project requires ~3.6.0. You can either downgrade your requirement or update magento/magento-coding-standard to a newer version that supports php_codesniffer ~3.6.0.
    • If downgrading is feasible for your project, modify your composer.json:

"squizlabs/php_codesniffer": "~3.3.0"

    • Alternatively, check if the magento-coding-standard has a newer version compatible with ~3.6.0 and update accordingly.

 

Magento Functional Testing Framework (MFTF) conflict:

  • The MFTF package also requires Guzzle 7.x, which conflicts with your Guzzle 6.5 requirement. Once you update Guzzle to 7.x as mentioned in step 2, this issue should resolve.

 

As a temporary workaround, you can try running the composer update with --ignore-platform-reqs to skip the platform checks:

 

composer update --ignore-platform-reqs

 

After following these steps, you should be able to update Magento and resolve the dependency conflicts.

 

If the issue will be resolved, Click Kudos & Accept as a Solution.