Troubleshooting
Here you can find a list of different problems along with possible solutions. Let us know, if anything is missing!
The Mollie plugin got a makeover recently when it comes to logging. This means that both, the quality and quantity of log entries did increase. Better logs mean easier and faster support - which might even help you directly before contacting the support.
If your log files take too much disk space in a short amount of time, then it means that you probably have lots of orders. In that case, please increase the "Log Level" in the plugin configuration to INFO or above (WARNING, ERROR). This will skip all DEBUG entries which are usually multiple entries for every order.
If you still face the same issue, then you might want to even increase to WARNING and skip the INFO messages.
If one or all payment methods do not exist in Shopware, please use the "Update Payment Methods" button in the plugin configuration, OR verify the following:
- Is your payment method unlocked and enabled in the Mollie Dashboard?
- Try to set either the LIVE Api Key + Test Mode ON, or the TEST Api Key + Test Mode OFF in the plugin configuration and import your payment methods again.
ERROR: Order is paid as a single payment (not an order) at Mollie
This error means that the Shopware order has been made using the "Payments API" and not the "Order API". That means there is only an existing transaction but no order in Mollie. Mollie transactions cannot be marked as "shipped". This is no bug, it's indeed as expected. Only orders in Mollie have this feature.
There should be no need to mark this order as "shipped".
If you want to use this feature for all payments and not only for Klarna, you might want to enable creating orders for ALL payment methods besides Klarna in the Plugin Configuration.
With one of the recent changes in Mollie, the process of a refund takes a bit. So if you start a refund, it's not automatically refunded and thus appears as "paid" in Shopware. Once the refund is complete, it will be automatically updated in Shopware using webhook notifications. You can open the transaction in the Mollie dashboard to see if a refund is in process.
After an update of the plugin, your orders might not work anymore, if not done correctly.
If that is the case, then it might be that new columns have been added to the database.
This leads to a very long SQL Error in the Shopware/Mollie logs. The last part of this error should show something like "Column not found".
This is a sample of such an error.
An exception occurred while executing 'SELECT m0_.id AS ……. ?' with params [\"mollie_klarnapaylater\"]:\n\nSQLSTATE[42S22]: Column not found: 1054 Unknown column 'm0_.bank_transfer_flow' in 'field list'"If that is happening to you, don't worry. You just need to clear your caches!
Every now and then, plugins might add new columns to the database for various features. Mollie, as well as other plugins, go with the usual procedure of doing such a thing in Shopware. This however requires that the caches have to be completely cleaned, so that Shopware is aware of the new columns.
If it is still not working, please see if the field exists in your database. This is usually in one of the tables that start with "mol_". The field name and table should be readable from the error message.
If the field is existing, then it has to be the caches. If it's not existing, please let us know, then it seems as if something went wrong during the updates.
If you're using LiteSpeed Cache for Shopware,
please make sure that you add /Mollie to the list of No-Cache URL paths in the Cache Plugin configuration.
That way you make sure that Mollie's responses and redirects always result in a full update and no responses or
status changes are cached in the LiteSpeed layer.
The impact on performance should be minimal, as we try to keep the operations on the /Mollie endpoints as lean as possible.
