Tag
Finding the actual cause when WordPress breaks.
WooCommerce
Check whether the specific notification is enabled, whether the order status actually triggers it, and whether the site can send mail at all — three separate failures with one symptom.
WooCommerce
A rejected coupon is usually doing exactly what it was configured to do. Read the error message, then check expiry, minimum spend, product restrictions and usage limits in that order.
Troubleshooting
Get back in first, then fix the delivery. The reset email failing is almost never about the account — it is the site's mail configuration, and it affects every other notification too.
Troubleshooting
A loopback is WordPress calling itself over HTTP. When it fails, cron, the editor's recovery features and the plugin editor stop working — and the cause is nearly always DNS, auth or a firewall.
Troubleshooting
Horizontal scrolling, tiny text and a broken menu each have a specific cause. Reproduce the problem in a device emulator, find the element that overflows, and fix the rule.
Troubleshooting
Scan with a crawler rather than a resident plugin, fix internal links at the source, and redirect only where a genuine equivalent exists. Deleting the link is often the right answer.
Troubleshooting
Corrupted tables produce missing content, failed saves and repair prompts. Back up first, then use WordPress's built-in repair, phpMyAdmin or the command line — in that order.
Troubleshooting
Cleaning malware is only half the job. Contain the site, replace core and extensions with clean copies, close the entry point, and rotate every credential before going public again.
Troubleshooting
A PHP upgrade breaks code that used removed syntax or relied on loose behaviour. Read the fatal error, identify the responsible plugin or theme, and roll back the version while you fix it.
Troubleshooting
The Site Editor needs a block theme, a reachable REST API and working JavaScript. Missing menu item, endless spinner and blank screen each point at a different one of the three.
Troubleshooting
A site rendering as plain text means the stylesheet request failed. Open the network tab, find the failing request, and fix the URL, the mixed-content block or the broken minified file.
Troubleshooting
Before touching WordPress, find out whether DNS resolves, the server answers and PHP runs. Each layer fails differently, and the browser message tells you which one to look at.