Diagnostics and health checks Free

Praetor → Diagnostics shows every check, with the failures first.

What is checked

• Platform — supported PHP, WordPress and WooCommerce versions.
• Database — every table and index Praetor owns. This one matters: WordPress’s schema helper reports success whether or not it created an index, so Praetor re-reads the live schema instead of trusting it.
• Migrations — whether a database update is pending, running or failed.
• Background jobs — whether Action Scheduler is available.
• Overlapping plugins — other active plugins that do a job an enabled module also does. This is advisory. Praetor never deactivates or edits another plugin; two plugins pricing the same basket is a decision for you to make on a staging site.
• Module isolation — that only enabled modules were instantiated on this request.
• Per-module checks — quantity rules that no quantity can satisfy, empty product tabs, duplicate document numbers, the checkout field API’s availability, and so on.

Praetor also reports into Tools → Site Health, which is where an agency looks first.

Support bundles

A support bundle collects environment facts, module state, schema state and health results. Before it is generated you see every field it would contain, and you can exclude sections.

Everything is redacted on the way out: email addresses, tokens, keys and anything that looks like one, at any depth. There is no customer data in a bundle.

Debug logging

Debug logging is off. If support asks you to turn it on, it writes through WooCommerce’s own logger and switches itself back off after seven days.

When you are not sure Praetor is the problem

Turn on safe mode. Every Praetor module stops running on the storefront while your settings stay exactly as they are. If the problem persists, it is not Praetor.