From this article, you will learn how to enable PrestaShop debugging mode to learn the details of ERROR 500 error.
HTTP Error 500, also known as "Internal Server Error," is a general message indicating that there is a problem on the server that prevents the store or server from working properly.
- Error 500 indicates that something has gone wrong on the server side, but does not specify exactly what problem has occurred.
- The causes of Error 500 can be varied: a problem with the server, database or modules, and other unexpected situations.
- To resolve Error 500, you need to learn the details behind the error.
Why should you learn to work with server errors?
With the details behind Error 500, you will be able to solve the problem yourself or get help faster on PrestaShop-related groups and discussion forums. Providing experienced users with precise details of the error will speed up the support process.
Debug mode in PrestaShop
PrestaShop has a debug mode (also called developer mode), which is disabled by default.
Debug mode provides additional error information and helps you identify where the problem occurred. Once debug mode is enabled, you can start debugging your store.
Debugging is essential when developing and optimizing your PrestaShop store, as it allows you to solve problems quickly and efficiently, which contributes to the smooth operation of your store and improved user experience.
What is PrestaShop debugging?
Debugging is a process in which you can learn about the problems behind the Error 500 error from the general to the detail. The details of the errors that occur will lead you to the files, modules or server settings that are causing the server to not work properly.
Enable debug mode in the defines.inc.pl file
In each version of PrestaShop 1.6, 1.7 and 8+, debug mode can be enabled by editing the file via FTP:
- Edit the file: config/defines.inc.php
- Find the _PS_MODE_DEV_ variable.
- Change its value from "false" to"true".
- Save the modified defines.inc.php file.
- Clear the cache - to do this, you can use the tools in the PrestaShop admin panel or manually delete the contents of the cache folder in the store's root directory.
- Refresh the page where the Error 500 occurred to see detailed error messages.
In PrestaShop 1.7 and 8+, you can enable debug mode in the Back Office
In PrestaShop 1.7 and 8+, you can also enable debug mode in the store's admin panel: Back Office > Performance > Debug Mode:
Remember to disable debug mode when you are done.
Read the error details
Access Error Logs on your server
PrestaShop generates logs that contain information about various store events, including errors. Going through these logs can help you locate a specific error and understand its cause.
If debug mode is disabled on your store, you can still see the history of errors that have occurred in the past.
Your server logs the details of all errors in logs. The server logs contain details including the dates on which any errors occurred in your store and on your server. It's worth checking the server logs regularly to track down errors that have occurred in the recent past.
Resolve problems
To get rid of the problem, you can restore the store backup or uninstall the module or modifications that are the source of the error. This is a half-hearted solution, as the module should ultimately work flawlessly in your store.
Fixing a store or module error that generates Error 500 requires programming knowledge. If you want to solve the problem professionally you should contact the programmer or agency that takes care of your store.
Providing the programmer with details about the history of the error and details of the error from the debug mode will make it easier to evaluate and quote for fixing the problem.
At PrestaShow, we develop PrestaShop modules and provide support for online stores. If you want to accelerate the development of your store and the eCommerce tools you use, and you want to protect yourself from errors, crashes and sales downtime - feel free to contact us.
