If a Pickware update fails in the Shopware Admin, the cause is often an outdated cache or database migrations that did not run. With the following steps, you can fix the most common errors yourself. If you installed Pickware via Composer, you will find the matching troubleshooting in How do I install Pickware via Composer?.
Attention: Create a backup before the update. If the update does not complete, restore this backup before you try again.
Errors right after the update: clear the cache
If errors such as ArgumentCountError, Too few arguments to function …::__construct() or Class … not found occur right after the update, the cache is mixing old and new parts of the extension. Proceed as follows:
Restore your backup.
Completely delete the
var/cachefolder of your shop. The commandbin/console cache:clearis not sufficient here because it leaves remnants behind. Alternatively, rename theprod_…folder in the cache.Open your shop or the Shopware Admin once so that the cache is rebuilt.
Start the update again.
If an ArgumentCountError appears only once right after the update, it is a side effect of the old cache. Once the cache is rebuilt, it disappears.
Errors caused by missing database migrations
Messages such as Table … doesn't exist, Unknown column … or a 500 error when deactivating indicate that database migrations did not run. In this case, run one of the two commands and then empty the cache:
bin/console system:update:finish
bin/console database:migrate --all
bin/console cache:clear
Note: When you only activate an extension, Shopware does not run any migrations. Therefore, update the extension again instead of only activating it.
Staging environment built from a database dump of the live shop
If you built your staging environment from a database dump of your live shop, the migration state often does not match the database. Run bin/console database:migrate --all on the staging environment. If errors with foreign keys such as Can't DROP FOREIGN KEY … appear, contact support and include the output of bin/console database:migration:status.
Table already exists
If the update reports Table … already exists even though the table was created correctly, the affected migration must be marked as executed in the Shopware table migration. In this case, contact support before you make any changes to the database.
Keep Pickware up to date
Many reported errors have already been fixed in newer Pickware versions. Therefore, update your Pickware extensions to the latest version before you look for other causes.
What support needs from you
If none of the steps help, contact Support. So that we can help you quickly, send us:
The complete error message
Your Shopware version and the version of the Pickware extension
Access to the Shopware Admin as well as SFTP or SSH access
You will find further tips in What can I do to get my support request answered faster?.