Error Logs

94 Aufrufe Markdown

Read the errors and warnings your installation records, grouped so that identical faults share one row, and tell which of them are still happening.

Opening the Screen

Open Tools, go to the action logs and choose Error Logs: {admin}/tools/actions/error-log

What Is on the Screen

The strip at the top answers the first question: is anything still going wrong. The table under it holds one row per distinct fault.

Verdict line One sentence for the most serious level seen in the last 24 hours, such as Errors are still occurring. The counts under it give three numbers. How many distinct faults exist, how many times they occurred in total, and how many were seen in the last 24 hours. A thin bar under them shows how the levels share that total.
Level buttons The counters are also filters: Fatal, Error, Warning, Info, Last 24 Hours and Database. Click one to narrow the list, and click it again to clear it. A button appears only when it has records behind it.
Recording On The badge at the right of the strip. It reads Recording Off when logging is switched off. New rows can still appear while it reads that, because the switch only covers database and template errors.
The table Four columns: Level, the error message, Occurrences and Last Seen. Under the message sit the file and line, the exception class and the client who hit it. Where the two dates differ, the first sighting sits under the last one.
Row menu The button at the end of a row offers View and Delete.
Download The trigger at the right end of the strip above the table, offering CSV, JSON and XML. The file holds the whole filtered list, not the page you are on. It also carries the type, file path, signature, first sighting, IP and request address the screen leaves out.

Fields

Recording settings

Click the Recording Settings button on the strip to open three switches. Each one saves the moment you change it.

Logging Keeps a record of database errors and template engine warnings. With it off, only those two stop; PHP errors, warnings and fatal errors are still recorded.
Debugging Shows detailed error messages and debugging information to anyone using the site.
Developer Mode Turns on developer mode and its extra debugging features.

Search and filters

The search box above the table matches the message text. The Advanced Filter button opens ten more boxes. They are Message contains, File path contains, Exception class, Request URI, Method, Min repeats, IP, Signature, User ID and Date range. Closing the panel clears every one of them.

Clear Logs dialog

Select Date Deletes the faults whose last sighting falls on or before that day. Required, and there is no default.
Enter your account password for security verification. Your own panel password. Required; a wrong password stops the deletion.
Apply to Selected The list above the table. Its one action is Delete Selected, which works on the rows you ticked.

Tasks

Read a fault in full

  1. Open the row menu and choose View.
  2. The dialog opens on Stack Trace. Request, Environment and Raw Data hold the address, the client, the PHP version and the stored variables.
  3. Copy Details at the bottom puts the whole record on your clipboard for a developer or a support ticket.

Delete records

  1. For one row, open its menu and choose Delete, then confirm with Delete Entry.
  2. For several, tick them, choose Delete Selected, fill in the password box and confirm with Delete Entries.
  3. The rows leave the list. Every occurrence they had gathered goes with them.

Clear records older than a date

  1. Click the Clear Logs button next to the page title.
  2. Pick a date, type your password and click Confirm.
  3. System and database records not seen since that day are removed, and the page reloads.

Switch recording on or off

  1. Click Recording Settings and use the Logging switch.
  2. The badge on the strip follows the switch, so you can see the new state without reloading.

Things to Watch

Debugging and Developer Mode are visible to your visitors

Both settings expose internal details such as file paths and stack traces to anyone using the site. Switching either one on asks you to accept the risk first. Keep them off on a live installation, and turn them on while you are working on it.

Deleting cannot be undone

A deleted row takes all of its repeated occurrences with it. Clearing by date removes the faults not seen since that day. One that is still recurring stays on the list, with its whole history. The diagnostic data is gone for good, so copy anything a developer still needs before you delete it.

A record says what happened, not what is happening

An old entry can describe a fault that was fixed weeks ago. Use the Last 24 Hours button and the last sighting date to tell a live problem from a historical one.

A record does not reveal where the installation lives

File paths are shown relative to the installation folder. The database name, the server account and the admin folder name are replaced with placeholders such as {db}. Nothing you copy from a record gives away the location of the installation.

Required Privileges

The screen and all of its actions need the TOOLS_ACTIONS privilege. Without it the page is not shown. Downloading the list needs TABLE_EXPORT as well, and without it the download trigger does not appear. Client and staff names in a row link to their records only where you also have access to those screens.

War das hilfreich?

Vielen Dank für Ihre Rückmeldung!

Brauchen Sie weitere Hilfe?

Unser Support-Team ist rund um die Uhr für Sie da, wenn Sie oben nicht fündig werden.

Kontakt aufnehmen Ticket eröffnen

Wir verwenden Cookies, um Sie angemeldet zu halten, Ihre Sprache und Währung zu merken und die Website zu verbessern. Cookie-Richtlinie