Skip to content

Topic hub · 1 guide

Diagnosing a broken site without guessing

A white screen, a checkout that fails, an order email that never arrives. The instinct is to disable plugins until something changes, which works often enough to be a habit and teaches you nothing when it does not. This hub covers the path that survives a hard case: reproduce the fault reliably, decide what class of thing it is, change one thing at a time, and keep a route back. The last step matters most, because the fastest way to turn a broken site into a lost site is a confident fix applied to the wrong layer.

What this hub covers

  • Reproducing the fault before changing anything
  • Plugin and theme conflicts
  • Faults that look like one cause and are another
  • When to stop and restore

Start here

How to troubleshoot a website: reproduce, isolate, change one thing: three rows of small product squares on a pale ground with a larger brand-coloured square and a dark price-tag shape
Guides

How to troubleshoot a website: reproduce, isolate, change one thing

The instinct is to disable plugins until something changes. It works often enough to become a habit and teaches you nothing when it does not. Here is the order that survives a hard case.

10 min read

Related topic hubs

Named across this hub: WordPress, WooCommerce, Shopify, PHP, MySQL, cPanel.

Put a real answer on every page.

Ask this site's own widget a question and watch it cite the page, or refuse. It is the same plugin, running on the same content you are reading.

Join the launch list Try the live demo