WordPress

Problems after WordPress 7.0? Learn what changed (PHP 7.4 minimum, iframed editor, pattern locking), which bugs 7.0.1 fixed, and how to roll back or report a bug.

Problems since WordPress 6.9? See the changes that broke sites (email sender, post navigation loops, classic theme styles), what 6.9.1 to 6.9.4 fixed, and how to roll back.

Customers report card fraud after buying from you, or a strange card form appears at checkout. Stop card payments, find the skimmer in the database and files, clean up and notify the right people.

The cart or checkout says no shipping options were found for an address. Turn on shipping debug mode to see which zone matched, then fix the zone order, ZIP codes, methods or carrier plugin.

Your site and email vanished and the domain now points somewhere else, or sits at a registrar you never used. Confirm what changed with RDAP, lock down the email behind the registrar login, then escalate through the registrar, the transfer dispute process and ICANN.

Your designer went quiet, closed their business or will not hand over the domain or hosting. Find out what you already control, prove you are the registrant, recover accounts in your own name, and rebuild access for anything you cannot get back.

You have just been handed a WordPress site you did not build. Work through it in a safe order: inventory and access first, an off-server backup before any change, then users, code integrity, licenses, updates and monitoring.

Visitors see a fake Cloudflare check that tells them to press Windows key + R and paste a command. Your site is hacked. Make the lure show itself, find the injected script, clean up and warn visitors.

An email says your site has a vulnerability, broke copyright, is about to lose its domain or will be suspended. Most are scams, some are real. Verify each one by logging in to the real account yourself, never through the link in the email.

Someone is in your mailbox: contacts get spam from you, replies vanish or your provider blocked sending. Lock the attacker out, remove their rules and forwarding, then get delisted.

PHP stopped a request because it hit the memory or time limit. Read the exact error, check the real limits, raise them in the right place for your panel, then find what keeps hitting them.

The site loads on mobile data but not on your Wi-Fi, or fails only in your office. Prove it is up, then check for a firewall block on your IP, stale DNS, IPv6 and local filters.