The Logs area is where Classic Commerce keeps logs of all events happening in your store. Go to Classic Commerce > Status > Logs. In the dropdown box, you can choose the level of logs you want to see. This can be useful to get exact errors with timestamps on parts of your store. If your site experiences a fatal error, they may be logged here under a log named
fatal-errors. This can assist with debugging.
By default, logs are kept for 30 days before being purged . This can be changed using the
woocommerce_logger_days_to_retain_logs filter which defaults to
Fatal Errors Log
Classic Commerce includes a log that displays PHP fatal errors. This log can contain pertinent information that would be found in the PHP error logs. It is a good place to start before moving to finding the PHP logs on the server.
To access the Classic Commerce Fatal Errors log:
- Go to Classic Commerce > Status > Logs
- Choose a log from the drop-down labeled
- Click View
The types of errors caught in this log are PHP fatal errors, runtime errors, and errors purposely triggered in the code by a PHP function. Runtime errors can occur when there is a typo in the code, for example.
Fatal errors occur when the action in the code cannot be completed. Examples of a fatal error include:
- Calling an undefined function
- Using an undefined variable
- Calling a function on a null or otherwise unusable variable
This does not include web server errors, such as timeouts.
The log will include the:
- Timestamp when the error occurred
- Error that occurred
- File and line in the code for the origination of the error
- Stack trace – a snapshot of the history of the function calls and files leading up to the error