New answers tagged

0

Restore the composer.lock file from your version control system that was used before you updated. The composer.lock exactly records which software was installed. So it is paramount to commit this file into version control in order to be able to go back to a working version in case of update failure. Running composer install will always install the software ...


0

Not using correct root user for cpanel.


0

myparcelnl/magento module is compatible with 2.4.x. I think issue in your composer.josn file. You need to update composer.json file, edit composer.josn file from your Magento's root path Step-1: Change version "version": "2.x.x" with "version": "2.4.2", Step-2: Update version under require, "magento/product-...


0

If you find yourself in this situation like I did it's possible you skipped the step in the cli upgrade process to update the additional packages. Please see the dev docs links: https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html In short the step "Specify Additional Packages" is what I missed which would've updated the additional ...


0

Use composer self-update --update-keys to update pubkeys. For example: Enter Dev / Snapshot Public Key (including lines with -----): -----BEGIN PUBLIC KEY----- MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA0Vi/2K6apCVj76nCnCl2 MQUPdK+A9eqkYBacXo2wQBYmyVlXm2/n/ZsX6pCLYPQTHyr5jXbkQzBw8SKqPdlh vA7NpbMeNCz7wP/AobvUXM8xQuXKbMDTY2uZ4O7sM+PfGbptKPBGLe8Z8d2sUnTO ...


0

This happened to me after accidentially duplicating my module to another place in app/code/. Solution: Delete the duplicate.


4

It appears that this error might appear when a MySQL database is empty, but the env.php file is present. (Possibly because you had setup Magento, but for some reason, database was deleted.) To fix this you can add --cleanup-database flag to setup:install command (For me, it went ok only after the second try.), or delete the env.php file indeed, which I don't ...


1

For windows rm -rf vendor && composer install For Ubuntu sudo rm -rf vendor && sudo composer install


0

Setting the filesystem ownership to the magento user (dev in my case, while before was assigned to www-data user) fixed the problem: chown -R dev:www-data .


Top 50 recent answers are included