Start with what the visitor cannot do
A critical error or HTTP 500 concerns the site's execution. A store that loads but cannot complete checkout has a different failure and acceptance test. Write the exact visitor sequence, affected product or page, first observed time and preceding update before changing plugins.
- Critical error: inspect existing application and host logs for a first relevant fatal error.
- Checkout failure: record whether failure occurs at cart, address, shipping, payment or order confirmation.
- Keep customer details and payment information out of screenshots and enquiry logs.
A staging copy is not automatically harmless
WooCommerce recommends a staging copy and backups for conflict testing. A clone can still contain live payment, email or integration settings. Agree an isolated test route, synthetic orders and disabled external effects before testing; merely changing the hostname does not make a copy safe.
- Keep a known restore point and name who can restore it.
- Use a test payment configuration approved by the account holder.
- Do not copy real customer records into an agent's workspace.
Find a cause, not a lucky combination
Compare the theme and plugin combinations systematically and repeat the same failing sequence. Host-managed must-use plugins, drop-ins and caches can survive ordinary deactivation. Record each combination and result; if re-enabling a component restores the failure, that is more useful than leaving everything disabled.
- Do not remove essential checkout capabilities simply to obtain a passing demonstration.
- After a fix, check an unaffected path as well as the original regression.
Choose an accountable repair
Request the named broken flow with a redacted error and change history. The scope should state included components, exclusions, test-order evidence, reversal and who approves a live change. This is a newly offered service catalogue, not evidence of previous customer deliveries or guaranteed conversion improvement.
Sources and limits
- WordPress: debugging Checked 2026-10-10.
- Debug logging and display can be separated; debug tools are intended for development or staging.
- WooCommerce: conflict testing Checked 2026-10-10.
- Backup and staging precede theme/plugin conflict isolation.
- Must-use plugins and drop-ins can remain active during ordinary plugin isolation.