Manage and monitor your WordPress website with ease using our WordPress Issue Tracker plugin. This powerful tool allows you to conveniently view and search WordPress logs, receive security advice, track 404 errors, and fine-tune your server settings.
We’ve designed the Issue Tracker plugin with accessibility and simplicity in mind. Say goodbye to the hassle of reading and searching through the debug.log file on your server. With the Issues Tracker, you can access and search logs directly within your CMS, making them easily readable and searchable.
Additionally, our plugin provides email notifications for various error events and covers more issues than a typical WP health checker.
Enhance your website’s security and performance with these key features:
Debug Log Viewer
Effortlessly view notices, warnings, and errors from the WordPress debug.log file in a user-friendly table format. Utilize advanced search options (by error type, line, and file) and pagination for quick and convenient log management.
WordPress 404 Errors
Identify and list all 404 (page not found) errors on your website, and configure email notifications for these events. For example, receive email alerts for every 404 event.
Receive expert recommendations on server and site settings to boost your website’s speed and security. Get notified via email if your server’s condition deteriorates.
Our plugin evaluates your website based on various criteria, including:
– Checking if the database username used in wp-config.php is widely used.
– Verifying the security of the database password in wp-config.php.
– Examining the state of the WP_DEBUG_DISPLAY constant.
– Ensuring you are not using the default database prefix.
– Verifying SSL (https) encryption status.
– Checking the PHP version for updates.
– Confirming that the WordPress version matches the HTML code.
…and many more checks in future releases.
Monitor all your website’s performance and security issues conveniently from one central location. Access log file entries, server checks, and 404 error reports in a single dashboard.
Unlock even more capabilities with our Pro version:
* Receive email notifications when the Advisor module detects security issues.
* Get alerted via email for every 404 request.
* Enjoy priority email support.
How to activate withing WordPress
- Go to ‘Plugins > Add New’
- Search for WP Issues tracker’
- Click install then activate
How to activate manually
- Upload the plugin files to the /wp-content/plugins/ directory, or install the plugin through the WordPress plugins screen directly.
- Activate the plugin through the « Plugins » page in Dashboard
How do I debug a WordPress website?
To debug a WordPress website, follow these steps:
* Enable needed switchers in header of Issues Tracker plugin.
* The server will log errors into the
wp-content/debug.logfile. You can search this log file directly on the server or within your CMS using the Issues Tracker plugin.
* Keep in mind that after enabling debug mode, your website’s behavior may change, and errors may be displayed to users or administrators.
For more detailed information, refer to the official WP debug guide.
Why is the debug.log important?
debug.logis a crucial component of the WordPress system for debugging code, encompassing core, plugins, and themes. It plays a vital role in ensuring code quality and the smooth operation of your website.
You should aim to maintain an empty
debug.logfile, free from notices, warnings, or critical errors. If a new line appears in the
debug.log, take prompt action to resolve the underlying code issue to provide the highest quality user experience for your website visitors.
What should I do with 404 errors on WordPress?
In WordPress, a 404 page is displayed when a requested page is not available, often accompanied by the message « Page Not Found. » These 404 errors indicate a need for improving the user experience. Numerous errors of this kind can deter users from your website and negatively impact search engine optimization.
Search engine crawlers do not index 404 pages, which can lead to a decrease in your website’s search result rankings. It’s essential to address and resolve 404 errors to enhance your website’s usability and SEO performance.
What are the common WordPress issues that can be tracked in the debug.log file?
debug.logfile serves as the default issue tracking log for WordPress. It provides valuable insights into various plugin errors. While some of these errors may not be critical immediately, they can lead to severe issues, such as the « White Screen of Death, » in the future.
Additionally, you can use the
debug.logfile to track errors in the code of the active theme. Regularly monitoring and addressing these issues is essential for maintaining the stability and functionality of your WordPress website.
Contributors & Developers
“Issues Tracker” is open source software. The following people have contributed to this plugin.Contributors
- General: checked compatibility with WordPress 6.3.1
- General: Updated Freemius SDK; Reduced plugin size
- General: Fixed bug with the Pro version of the plugin
- General: Added links to support form and forum
- General: checked compatibility with WordPress 6.1.1
- Log viewer: Added switchers for changing debug constants values
- Advisor: Added free disk space check (beta)
- Advisor: Applied template for Emails
- Dashboard: Fixed wrong checks count
- Advisor: Fixed wrong name of checks
- Advisor: Added progress-bar
- 404: Added recheck URL functionality
- 404: Added remove URL functionality
- General: Updated Freemius SDK
- General: Tested with WordPress 5.9.2
- Log viewer: added support of logs with overrided path in WP_DEBUG_LOG(‘path/to/log.txt’);
- General: added ability to translate an interface of the plugin
- 404: Fixed « loading » when no data presented in the table
- Advisor: minor fixes
- Advisor: Added daily checks and notifications about security issues
- General: Fixed typos
- Improved design (UI)
- Added 404 catcher with notifications (Pro plan only)
- Improved performance
- Bugs fixes
- Dashboard: a little changed UI
- Log viewer: increased debug.log limit from 20 to 100Mb
- General: added Freemius
- General: changed logo
- Log viewer: Fixed row direction (from newest to oldest)
- Advisor: Added check is WordPress version is showed in HTML code of a site
- Advisor: Added check is WP_DEBUG_DISPLAY is enabled
- Fixed typos
- Added message in case is debug.log is not found
- Initial release