Errors Log
Go to System → Logs → Error Log.
The Error Log viewer reads log files written by AbanteCart core, scheduled tasks, and any extension that writes to the log directory. Use it to investigate problems with checkout, payments, shipping rate calls, scheduled tasks, or admin actions.
Select a log file
The dropdown at the top of the page lists every .log and .txt file the viewer can read. The selector now covers:
Files directly in
system/logs/.Files in immediate subdirectories of
system/logs/(one level deep). Extensions and scheduled tasks often write their own subfolder, for example,system/logs/tasks/.
Each entry shows the file path relative to system/logs/ and the file size next to it, so you can spot a runaway log quickly. Picking a different file from the dropdown reloads the viewer with that file's contents.
Default log file
The default file shown when you open the page is whatever Error Log Filename is set to in System → Settings → System. The default is error.txt, written by AbanteCart core for uncaught exceptions and warnings.
Reading the log
Each entry that starts with a timestamp in YYYY-MM-DD HH:MM:SS format is grouped into a single row. The timestamp is bolded and any continuation lines that follow without a new timestamp are stitched onto the same row.
Large files. When the selected log file is larger than 500 KB, the viewer shows only the last 500 KB and prints a header noting the truncation along with the full path on disk. To see the rest, download the file from the server with FTP or SSH.
Clear the current log
Click Clear Log to truncate the file currently selected in the dropdown. The action removes the file's contents (and the file itself); a fresh file is created the next time AbanteCart writes a log entry. The button only acts on the file shown in the dropdown, not on every log file at once.
Disable error logging
To stop writing new entries entirely, open System → Settings → System and turn off the Log Errors setting. Existing log files stay where they are; only new writes are suppressed.
Leaving error logging off in production hides the diagnostic information you will need the next time something breaks. Disable it only briefly while investigating a specific issue or to silence a known-noisy log temporarily.
Direct file access
If you cannot reach the admin (for example, during a fatal error early in the request lifecycle), the same files are on disk at:
/system/logs/error.txt
and other files under /system/logs/ and its immediate subdirectories. Use FTP or SSH to download them.
Extension and scheduled task logs
Many extensions write their own debug output into system/logs/ when their debug toggle is on. Examples:
The USPS extension writes USPS API requests and responses when Debug Logging Status is on.
PayPal Commerce writes payment-related debug entries with sensitive tokens masked.
Scheduled tasks write to
task_log.txt(and totasks.logfor the cron wrapper) so you can review what ran and when.
All of these files appear in the file dropdown automatically as long as their extension uses the .log or .txt filename convention and writes inside system/logs/.