Tag
Finding the actual cause when WordPress breaks.
Troubleshooting
When a site works everywhere except one browser, the site is usually fine. Prove where the fault lives with four tests, then fix the extension, the cache, the certificate or the CSS that only that browser cares about.
Troubleshooting
Mixed content means an HTTPS page is pulling something over HTTP. The padlock disappears, scripts get blocked outright, and the fix is to correct the stored URLs rather than to rewrite them on every request.
Troubleshooting
Two rows in wp_options decide which theme is active. Editing them works, but it is the third thing to try — not the first — and never without a backup.
Troubleshooting
A page that will not scroll is almost never a WordPress fault. Something left a scroll lock switched on, and the cure is to find what opened it rather than to force the page open with CSS.
Troubleshooting
If the page renders publicly but the editor is empty, your content is safe and the editor is what failed. That distinction decides the entire diagnosis, and it takes one browser tab to establish.
Troubleshooting
Open the logo's image URL on its own before you touch a single setting. That one check splits the problem cleanly into a caching fault and an override fault, and they have nothing in common.
Troubleshooting
At least four different things display something that looks like your site title, and Settings, General only controls one of them. Work out which one you are staring at and the fix takes a minute.
Troubleshooting
Every active plugin runs in the same PHP process, the same hook system and the same page of JavaScript. Conflicts are collisions in that shared space, and the collision type tells you which fix will hold.
Troubleshooting
"wp-admin is broken" is four unrelated faults wearing the same URL. The symptom you see — blank, redirect, 403 or 404 — tells you which one you have before you change anything.
Plugins
Database plugins fall into four groups that solve unrelated problems, and the cleanup category is the one most likely to break a site. Know which job you are doing before you install anything.
Troubleshooting
Half of these reports are not faults at all. WooCommerce hides a tab that has nothing to display, so the first question is never why the tab broke but whether it had any reason to appear.
Troubleshooting
WooCommerce Analytics does not read your orders. It reads a set of lookup tables built from them, and the historical import is what fills those tables — which is why a stalled import and wrong report figures are the same problem seen from two angles.