The WordPress Guy Blog
Business & Strategy
UK employment rights changes are here: what this means for your SME
The Employment Rights Act 2025 is not a future concern. Its first major wave of changes took effect on 6 April 2026, and if you run an SME in the UK, several of those changes carry direct financial consequences that start from the moment an employee joins your business or calls in sick. This is
Performance Optimisation
Advanced Techniques for WooCommerce Speed Optimization
Every pound you spend on paid search, social ads, or email campaigns is pointing potential customers at a door. If that door opens slowly, they leave. missed sales and damaged reputation are the direct result of a WooCommerce store that fails to meet basic speed expectations, and the customers who leave rarely come back to
Security Hardening
Authenticated Arbitrary File Upload Vulnerability Patched in Slider Revolution 7 WordPress Plugin
Slider Revolution is installed on millions of WordPress sites worldwide. If yours is among them, a recently disclosed security flaw means any logged-in user on your site — a newsletter subscriber, a low-level team member, anyone with the most basic account — could upload a malicious file and gain complete control of your server. That
Patch Tuesday, February 2026 Edition
Microsoft’s February 2026 Patch Tuesday fixed 58 security flaws across Windows and related software, six of which were already being used against real targets at the moment the patches dropped. That last detail is the one that matters. These are not theoretical risks being disclosed responsibly ahead of any known exploitation. Attackers were already inside
Attackers Actively Exploiting Critical Vulnerability in Breeze Cache Plugin
A critical vulnerability in the Breeze Cache WordPress plugin was publicly disclosed on 22nd April 2026, and attackers are already moving against sites that have not been patched. The flaw affects an estimated 400,000 active installations. What makes this particularly serious is that no login credentials are required to exploit it. An attacker with no
Troubleshooting
WordPress 7.0 Release Candidate 3
WordPress 7.0 is scheduled to release on 20 May 2026. If your business runs on WordPress, that date is close enough to warrant action now rather than after the fact. The question is not whether to update, but how to do it without taking a trading site offline or breaking functionality your customers depend on.
WordPress 7.0 Release Candidate 3
WordPress 7.0 lands on 20 May 2026. That is a firm date, but it is also a revised one. The core team’s March announcement confirmed that the original 9 April release was pushed back because the database architecture underpinning Real-Time Collaboration could not be resolved in time. That delay matters beyond the calendar: it tells
WooCommerce
WordPress 7.0 Beta 3
WordPress 7.0 Beta 3 landed on 5 March 2026, carrying more than 148 updates and fixes since Beta 2 — 70 in the Editor and 78 in Core. That volume of change in a single beta cycle tells you something about the complexity of this release. If you run a WooCommerce store, the arrival of
WordPress 7.0 Beta 5
WordPress 7.0 is now in late beta testing, and if you run a WooCommerce store, the clock is ticking on a decision you need to make before 20 May 2026. Not about whether to upgrade. About how to upgrade, and when. Beta 5 landed in March with more than 101 fixes since Beta 3, which
WordPress 7.0 Release Candidate 1
WordPress 7.0 Release Candidate 1 has landed, and if you are running a WooCommerce store, this is not a release you can afford to treat like a routine update and forget about. This is the most significant WordPress core release in years, and it has already had its timeline shifted once. Understanding what changed, why
Let's talk WordPress!
Whether you need a new site, improvements to your existing one, or technical support, I'm here to help. The quickest way to reach me is through this form - just tell me about your project and I'll get back to you promptly. Alternatively, you can call me on (01501) 404234 or email me at contact@wpguy.uk.
Partners
I've worked with
