Read errors
In production mode, only general error messages are output for security reasons. For debugging, the error messages must first be made readable.
Last updated
In production mode, only general error messages are output for security reasons. For debugging, the error messages must first be made readable.
Last updated
When Shopware is running in production mode, in most cases only general messages are issued, based on which it is not necessarily possible to identify the cause of an error. These messages often look like this:
A complete debugging guide can be found here:
https://docs.shopware.com/en/en/shopware-6-en/tutorials-and-faq/debugging
To be able to read out and debug the actual error message, the developer mode should be enabled. This is quite simple and should be done quickly before creating a support ticket - it will save your time in the end.
In the general configuration file of Shopware you can enable the developer mode. The file ".env" (from SW 6.6 ".env.local") can be found in the root directory of your Shopware installation on the server.
Please note that files whose filenames start with a "." are hidden by default and it may therefore be necessary to show them via a program setting depending on the directory call.
In the .env / .env.local file there is a variable APP_ENV . Change the value of this line from
in
Save this file again and empty the cache of the store in the administration.
The messages in developer mode are much more detailed. Instead of the "Oops! An Error Occured" error message, you will see a meaningful message about the error. After reading and copying the message you can deactivate the developer mode again.
If you do not know what to do with the error message, you can send it directly (as a screenshot) when opening a support ticket. Often you can tell from the information in the error message which extension is the cause of the problem. This saves you time and you can contact the right manufacturer directly.
