How to Use Staq Debug for Troubleshooting Issues

If you’re encountering issues on your WordPress site, such as:

• Critical errors
• Server 500 errors
• Page builders (like Elementor) not functioning correctly, e.g., the widget panel keeps spinning
• Other unexpected behavior like plugin conflicts or pages failing to load

Staq Debug is a simple and effective tool to identify the root cause of the problem. Below is a step-by-step guide to using Staq Debug for troubleshooting.

Steps to Use Staq Debug

Step 1: Open the Staq Debug Tool

1. Log in to your Staq account and navigate to the site in question.
2. Open the site’s Staq Panel.
3. Click on Debug

then enable the WP_DEBUG feature by clicking Enable WP_Debug.

Step 2: Use Your Browser Console

1. Open your browser (e.g., Chrome) and navigate to the page where the issue is occurring.
2. Right-click anywhere on the page and select Inspect.
3. Go to the Console tab and look for any errors, such as 500 errors or JavaScript-related issues.
4. Make a note of these errors as they often provide hints about the problem.

Step 3: View Debug Logs

1. Go to the page that has the issue i.e. critical error, widget forever spinning etc and refresh that page while the debug is now enabled
2. Go back to the Staq Debug section in the Staq Panel.
3. Click on the WordPress tab and hit the Refresh button.
4. Review the debug logs for error messages or warnings. These logs can reveal issues with plugins, themes, or database queries.

—

Example Scenario: Elementor Loading Issue

Let’s consider an example where Elementor widget panel keeps spinning. The loading icon gets stuck, making the page builder not accessible. To debug this, follow the steps below:

1. Enable WP_Debug in the Staq Debug tool as described above.
2. Open a page in Elementor and simultaneously open the browser’s Inspect Console.
3. Note the 500 error appearing in the Console.
4. Go back to the Staq Debug tool, refresh the logs, and look for errors related to Elementor or associated plugins.
5. In this case, the debug logs should show a plugin that is conflicting. When in doubt, copy the error code and place into ChatGPT and ask it to explain it to you in plain English
6. Disable the conflicting plugin.

Another Example: Memory

It might not be a conflicting plugin issue but a memory issue. Staq Debug will tell you if it’s a memory issue. If you need to scale memory up, see this knowledge base article on how to increase memory resources.

Disable WP_Debug

Once you’ve identified and resolved the issue, return to the Staq Panel and disable WP_Debug. Leaving debugging enabled for extended periods may slow down your site.

Additional Resources for Advanced Debugging

For more in-depth troubleshooting, consider the following guides:

• How to Use Query Monitor Plugin
• How to Use Staq Query Tool to Diagnose Database Queries

Important Notes

– Avoid adding custom debug snippets into your child theme. Instead, always use Staq Debug for better integration with server-side logging.
– Remember to clear any caching (e.g., via Staq Cache or other caching plugins) after making changes to ensure the issue is fully resolved.

Conclusion

Staq Debug is a powerful tool that simplifies the debugging process. By combining it with browser developer tools and the provided additional resources, you can quickly identify and resolve most issues on your site. Always disable WP_Debug after completing your debugging session to optimize site performance.