Technical guides, diagnostic walkthroughs, and update notices from the WPerizo team. Everything here is WordPress and WooCommerce – written by the people who work on it daily.
Your customers are asking ChatGPT, Claude and Perplexity the questions your blog answers — and none of them are on Google. Ranking well has stopped being the same thing as being readable. Four things we fixed on our own site last week, including one mistake we’d been making for months.
Your site went down overnight and nobody touched it. Elementor auto-updated to 4.3, and your Elementor Pro is too old to load alongside it. Updating further doesn’t help — 4.3.1 and 4.3.2 carry the same fault. Here’s how to get back online manually in the next ten minutes, and why this will happen again with a different plugin.
WordPress 7.1.2 arrived on September 22, five days after 7.1.1. One fix, critical severity: an unauthenticated attacker can make page template resolution load a PHP file from outside your theme — and under the right conditions, run it. Here’s what that actually means, why you can’t self-assess your exposure, and what to do in the next hour.
WordPress 7.1.1 landed on September 17 with 11 security fixes. One of them can be triggered by a visitor with no account. Several more need only a Contributor login — which is exactly what membership sites, multi-author blogs and WooCommerce stores with staff accounts hand out by default. Here’s what’s in it and what to verify afterwards.
Every WordPress site we rescue has the same story: an update ran, something broke, nobody knows what. Here’s why it happens, why “just update everything” and “never update” both end badly, and what a real update process looks like.
Almost every guide starts with “check your credentials in wp-config.php.” If your site was working yesterday and nobody edited that file, your credentials are fine — and you’re about to waste twenty minutes. Here’s what the error actually means, what causes it far more often, and why the standard advice to run WordPress database repair can make things worse on a WooCommerce store.
Most hacked-site guides start with “scan and clean.” That’s step four. Doing it first is why sites get reinfected within days — here’s the sequence that actually holds, in the order we run it on client emergencies.
Every 7.1 roundup lists the same features. This one covers the two changes most likely to break your site — the fully iframed post editor and redefinable breakpoints — plus the one that quietly fixes your image uploads. And the order to update in.
A blank white page isn’t a WordPress error. It’s the absence of one — PHP died before it could tell you what went wrong. Here’s how to get the error message back, and the order to check nine causes so you find yours in minutes instead of hours.
Your homepage scores 95. Your checkout crawls. That’s not a coincidence — cart and checkout can never be cached, so every inefficiency your site hides behind the cache happens in front of the customer. Four specific causes, how to measure which one is yours, and what to fix first.
WordPress 7.0.4 patches a remote code execution flaw. Most people clicked “Update Now” and moved on — here’s the part almost nobody does: seven things to verify afterwards, because an update that reports success isn’t the same as an update that worked.
