Before you start
- A repeatable failure scenario and involved software versions.
- An isolated copy without live payments or customer emails.
Run deactivation tests on the copy. Disabling live plugins can interrupt orders and payments.
Define a repeatable test
A conflict means components interact incorrectly; randomly disabling a plugin does not establish the cause. Describe the exact failing journey, versions and expected result. A visitor-only issue may remain invisible in your administrator session.
- Record page, product, browser, time and recent changes.
- Repeat identical steps after each change to compare results.
- Prepare a scenario without real customer data or payments.
Create an isolated copy
Back up files and database, then prepare a test copy. Prevent live payments, renewals and customer messages. The copy must reproduce the problem before testing; otherwise environmental differences can mislead diagnosis.
- Check versions and caching on the copy.
- Protect access and any customer information it contains.
- Keep the original list of active components before deactivation.
Test the theme separately
On the copy, use a reference theme compatible with the store and repeat the scenario. If the error disappears, investigate the original theme, child theme and customizations. If it persists, continue without assuming the theme can never contribute.
- Compare the same function and product.
- Do not change the theme and all plugins simultaneously.
- Record the outcome and retain a reference configuration for the next test.
Reduce plugins to the necessary minimum
On the copy, deactivate plugins unnecessary for the scenario. For payment testing, retain WooCommerce and the relevant gateway. Repeat the test, then progressively reactivate components until the failure returns. The latest activation identifies an interaction to examine.
- Test after each reactivation and record involved versions.
- For many plugins, test groups first and then isolate within the failing group.
- Keep security tools and external services controlled throughout testing.
Examine caching and special components
Caching can show an old page despite changes. Must-use plugins and some caching components cannot be disabled like ordinary plugins. If the minimal test still fails, review logs and differences between copy and production.
- Check browser, plugin, server and CDN caches actually present.
- Do not remove a mandatory component or cache file without understanding its purpose.
- For failures involving an external service, inspect its response too.
Correct and document the result
A fix may involve a compatible update, setting or replacement component. Give publishers a minimal scenario and versions without publicly exposing credentials or customer information. Apply the validated change to production with a backup.
- Test adjacent functions, not only the repaired feature.
- For WooCommerce, check cart, checkout, accounts and emails afterwards.
- Keep a record of cause and solution to prevent recurrence during later updates.
Official documentation
Labels and options vary with versions, plugins and your account. Refer to publisher documentation for your configuration.