# PHP Error Logging

#### Instant Visibility of Issues

<figure><img src="/files/EToUaL4DRUAVTx80giam" alt=""><figcaption></figcaption></figure>

At the top of the page, you’ll be notified if Varsuite Core has detected errors:

> **“We detected X different errors on your site”**

These can range from critical execution-halting issues to minor notices or deprecated function usage.

***

#### Error Log Table Breakdown

Each error entry contains:

* **Origin**\
  File path and line number where the issue occurred.
* **Message**\
  Full PHP error message including detailed **stack trace**.
* **Last Occurred**\
  Timestamp of the most recent occurrence of that error.
* **Occurrences**\
  Number of times that error has been triggered.
* **Actions**\
  Option to **DELETE** the individual error log or use **DELETE ALL ERROR LOGS** to clear the full log history.

***

#### Filter by Error Type

Varsuite Core provides granular filtering to help you isolate the most relevant errors. You can filter by:

| Error Category        | Description                                                        |
| --------------------- | ------------------------------------------------------------------ |
| **Error**             | General PHP runtime error                                          |
| **Warning**           | Non-fatal issue that may affect execution                          |
| **Parse Error**       | Syntax error that prevents script execution                        |
| **Notice**            | Informational messages about code quality                          |
| **Core Error**        | Serious errors in the PHP core                                     |
| **Core Warning**      | Warnings triggered by core-level PHP operations                    |
| **Compile Error**     | Errors during the script compilation phase                         |
| **Compile Warning**   | Non-fatal issues during script compilation                         |
| **User Error**        | Manually triggered user-defined errors                             |
| **User Warning**      | Custom warnings triggered via `trigger_error()`                    |
| **User Notice**       | Informational user-defined messages                                |
| **Strict**            | Code that doesn't adhere to PHP best practices or future standards |
| **Recoverable Error** | Errors that can be caught by a custom error handler                |
| **Deprecated**        | Use of outdated PHP functions or features                          |
| **User Deprecated**   | Manually flagged deprecated behaviour                              |
| **All Errors**        | View the entire log (can be tens of thousands of entries)          |

***

#### Developer-Focused Debugging

Each entry includes a stack trace, like:

> `Uncaught Error: Call to undefined method ActionScheduler::run()...`

This helps developers:

* Quickly find the file, line, and context of the error
* Trace dependencies and plugin conflicts
* Diagnose failed backups, plugin crashes, or API integration issues

***

#### Safe, Secure, and No Server Access Needed

* No need to SSH into the server or access `/var/logs/` or cPanel.
* Error logs are fetched securely via the Varsuite plugin and only visible within your dashboard.
* Logs can be cleared with a single click, keeping your environment tidy and focused on current issues.

***

#### Best Practices

* **Review after updates** – Always check logs after plugin/theme or core updates.
* **Keep logs tidy** – Clear old or fixed issues to focus on active errors.
* **Set Alerts** – Combine with **Monitoring > Alert Rules** to notify your team when critical errors are detected or increase in volume.

***

#### Ideal for:

* Development teams tracking plugin conflicts
* Agencies ensuring high-quality client rollouts
* Debugging staging or production environment issues
* Catching deprecated usage before PHP version upgrades

***

The **Site Error Logs** page is your all-in-one error intelligence dashboard giving you confidence, control and clarity over your site’s stability without touching a server or combing through log files.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vs-core.com/website-monitoring/php-error-logging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.