Magento 2.4-p1
Smartwave Porto
13 Amasty extensions
I am having terrible problems with extensions from Amasty. Now I need to untick/uncheck the ‘Billing address is same as Shipping address’ and I can’t do that due to Amasty’s extensions changed the check-out (namely the One-Step-checkout extension which we have disabled but is still installed). Amasty claims there is an option to untick this in the latest version of their One-Step checkout but I am unable to update any of their extensions due to the following Error:
I run:
composer update*
And this is the Error:
Problem 1
- magento/payment-services[1.4.0, ..., 1.4.1] require magento/module-payment-services-saas-export 1.4.* -> satisfiable by magento/module-payment-services-saas-export[1.4.0, 1.4.1].
- magento/payment-services[1.3.0, ..., 1.3.1] require magento/module-payment-services-saas-export 1.3.* -> satisfiable by magento/module-payment-services-saas-export[1.3.0, 1.3.1].
- magento/payment-services[1.5.0, ..., 1.5.1] require magento/module-payment-services-saas-export 1.5.* -> satisfiable by magento/module-payment-services-saas-export[1.5.0, 1.5.1].
- magento/module-payment-services-saas-export[1.4.0, ..., 1.4.1] require magento/services-connector ^1.2.2 -> satisfiable by magento/services-connector[1.2.3, 1.2.4].
- magento/module-payment-services-saas-export[1.3.0, ..., 1.3.1] require magento/services-connector ^1.2.1 -> satisfiable by magento/services-connector[1.2.1, 1.2.3, 1.2.4].
- magento/module-payment-services-saas-export[1.5.0, ..., 1.5.1] require magento/services-connector ^1.2.3 -> satisfiable by magento/services-connector[1.2.3, 1.2.4].
- magento/services-connector[1.2.1, ..., 1.2.4] require firebase/php-jwt ^6.0.0 -> found firebase/php-jwt[v6.0.0, ..., v6.3.1] but the package is fixed to v5.5.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires magento/payment-services ^1.3 -> satisfiable by magento/payment-services[1.3.0, ..., 1.5.1].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
I’ve raised this to Amasty and they came back to me with the following:
I’ve reviewed it with our specialists, and they confirmed that the difficulty seems to be related to the default Magento, I’m afraid. Unfortunately, it seems that some default extensions were not updated properly when updating Magento itself.
Please let me point out that the functionality of our extension strongly depends on the proper performance of the default Magento features. As the issue occurs on the side of the default Magento, its behavior should be fixed first. I’m afraid, according to our Policy, the Support Team developers are not allowed to troubleshoot the difficulties that are not related to Amasty extensions. So please, contact Magento support team and ask them to fix the issue for you.
How do I resolve the Errors and is it true this is a Magento issue and has nothing to do with Amasty? I’ve installed Magento 2.4.2-p1 and never update it in any way!
This is an EMERGENCY – someone please help! I did what Tu Van suggested below and it brought my whole website down!
I ran the following command via Putty (SSH):
composer update
And it now shows this Error on the front end (website):
1 exception(s):
Exception #0 (MagentoFrameworkExceptionLocalizedException): Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory.
The following modules are outdated:
Amasty_CheckoutCore schema: current version - 1.0.0, required version - 1.1.0
Amasty_CheckoutCore data: current version - 1.0.0, required version - 1.1.0
Magecomp_Smspro schema: current version - 1.0.7, required version - 1.0.9
Magecomp_Smspro data: current version - 1.0.7, required version - 1.0.9
Exception #0 (MagentoFrameworkExceptionLocalizedException): Please upgrade your database: Run "bin/magento setup:upgrade" from the Magento root directory.
The following modules are outdated:
Amasty_CheckoutCore schema: current version - 1.0.0, required version - 1.1.0
Amasty_CheckoutCore data: current version - 1.0.0, required version - 1.1.0
Magecomp_Smspro schema: current version - 1.0.7, required version - 1.0.9
Magecomp_Smspro data: current version - 1.0.7, required version - 1.0.9
<pre>#1 MagentoFrameworkAppFrontControllerInterceptor->MagentoFrameworkInterception{closure}() called at [vendor/amasty/aminvisiblecaptcha/Plugin/Framework/App/FrontControllerInterface/ValidateCaptcha.php:123]
#2 AmastyInvisibleCaptchaPluginFrameworkAppFrontControllerInterfaceValidateCaptcha->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:151]
#3 MagentoFrameworkAppFrontControllerInterceptor->MagentoFrameworkInterception{closure}() called at [vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php:71]
#4 MagentoPageCacheModelAppFrontControllerBuiltinPlugin->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:151]
#5 MagentoFrameworkAppFrontControllerInterceptor->MagentoFrameworkInterception{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:169]
#6 MagentoFrameworkAppFrontControllerInterceptor->___callPlugins() called at [generated/code/Magento/Framework/App/FrontController/Interceptor.php:23]
#7 MagentoFrameworkAppFrontControllerInterceptor->dispatch() called at [vendor/magento/framework/App/Http.php:116]
#8 MagentoFrameworkAppHttp->launch() called at [generated/code/Magento/Framework/App/Http/Interceptor.php:23]
#9 MagentoFrameworkAppHttpInterceptor->launch() called at [vendor/magento/framework/App/Bootstrap.php:263]
#10 MagentoFrameworkAppBootstrap->run() called at [pub/index.php:29]
</pre>