Frequently Asked Questions

WP Log Everything requires PHP version 7.4 or higher, and WordPress version 6.0 or higher.

The free version of Logtastic provides all the basic features required to implement logging on your website, including limited community support via the WordPress.org forums.

The pro version of Logtastic provides enhanced and additional features, including alerts and notifications, and advanced access and security options, alongside dedicated priority support via our support ticket system.

For a full feature comparison, please see the pricing page.

The first release of the Logtastic plugin focuses on error logging in WordPress, capturing PHP and JavaScript errors. Take a look at our roadmap for our planned future features, including HTTP request logging, email logging and more.

The PHP error log can capture all PHP errors, including fatal errors, uncaught exceptions and recoverable errors. You can configure which error types are captured from the log settings.

The PHP error log will capture the following data for each error:

• Error message
• File
• Line number
• Error source (plugin, theme or WP core)
• First occurred date/time
• Last occurred date/time
• Number of occurrences

For each occurrence of an error, the following additional data will be captured:

• Date/time
• WordPress version
• PHP version
• Plugin/theme version (if applicable)
• Full stack trace (optional)
• Affected user (pro version only)

The Logtastic plugin uses 3 methods to capture PHP errors on your WordPress site:

• Custom Error Handler
  The plugin defines a custom error handler that will capture all recoverable PHP errors on your site, for example warnings.
  
  
• Custom Exception Handler
  The plugin defines a custom error handler that will capture all uncaught exceptions on your WordPress site. Uncaught exceptions will proceed to generate a fatal error if left uncaught – as such, the plugin logs these uncaught exceptions as fatal errors.
  
  
• Shutdown Function
  The plugin defines a custom shutdown function, which will run after PHP has finished executing the current script. This captures any fatal errors which were not the result of uncaught exceptions.
  

Each function will determine whether or not the error should be logged, based on your log settings, and log the error/occurrence if it meets your defined criteria.

Logtastic leverages custom database tables to efficiently store and manage data, ensuring faster queries, reduced bloat in default WordPress tables, and improved scalability. By separating logs from core WP data, it delivers better performance, cleaner organization, and greater flexibility for advanced reporting and data handling—making it ideal for high-traffic sites and large-volume workloads.

The PHP error log uses the following tables to store data:

• logtastic_php_errors
  Creates an entry for each unique error and stores basic error data, such as file, line, error message, source and the error’s ignore status.
  
  
• logtastic_php_error_occurrences
  Creates an entry for each occurrence of an error and stores the related error id, time/date of the occurrence as well as PHP, WordPress and theme/plugin version information, and linked stack trace id (if applicable)
  
  
• logtastic_php_error_stack_traces
  If stack trace logging is enabled, creates an entry for each unique stack trace storing the full stack trace data (and arguments, if argument logging is enabled).
  

Our plugin is designed to have minimal impact on performance. It stores log entries in optimized custom database tables rather than crowding WordPress core tables, allowing it to write and retrieve data efficiently even on high-traffic sites. Logging runs in the background with lightweight queries, meaning your site continues to operate smoothly while still capturing valuable information for debugging and monitoring.

The JavaScript error log can capture runtime errors (errors that occur while code is executing, e.g. calling an undefined function or accessing a missing variable) and unhandled promise rejections (failures from promises – async operations – that aren’t caught with a .catch() or try…catch).

The JavaScript error log will capture the following data for each error:

• Error message
• Source
• Line and column number
• Error source (plugin, theme or WP core)
• First occurred date/time
• Last occurred date/time
• Number of occurrences

For each occurrence of an error, the following additional data will be captured:

• Date/time
• WordPress version
• Plugin/theme version (if applicable)
• Stack trace (optional)
• Additional session information, including the url where the error was encountered and the user agent (optional)
• Affected user (pro version only)

The Logtastic plugin loads a lightweight JavaScript file (less than 4kb) on each page of your WordPress site. The JavaScript will listen for errors, and when encountered will capture the error, process the stack trace and send this via an Ajax request to the backend logging function.

The backend logging function will determine whether or not the error should be logged, based on your log settings, and log the error/occurrence if it meets your defined criteria.

Logtastic leverages custom database tables to efficiently store and manage data, ensuring faster queries, reduced bloat in default WordPress tables, and improved scalability. By separating logs from core WP data, it delivers better performance, cleaner organization, and greater flexibility for advanced reporting and data handling—making it ideal for high-traffic sites and large-volume workloads.

The JavaScript error log uses the following tables to store data:

• logtastic_js_errors
  Creates an entry for each unique error and stores basic error data, such as file, line, column, error message, source and the error’s ignore status.
  
  
• logtastic_js_error_occurrences
  Creates an entry for each occurrence of an error and stores the related error id, time/date of the occurrence as well as WordPress and theme/plugin version information, and linked stack trace id (if applicable)
  
  
• logtastic_js_error_stack_traces
  If stack trace logging is enabled, creates an entry for each unique stack trace storing the stack trace data.
  

Our plugin is designed to have minimal impact on performance. It stores log entries in optimized custom database tables rather than crowding WordPress core tables, allowing it to write and retrieve data efficiently even on high-traffic sites. Logging runs in the background with lightweight queries, meaning your site continues to operate smoothly while still capturing valuable information for debugging and monitoring.