HOSTING TIPS ARCHIVE
WordPress: hosting guides
Practical steps and checks for hosting, WordPress and performance. Browse a topic or use the dates to explore the experience behind the advice.
15 guides, newest work first.
PHP 8.6 for WordPress: compatibility checks
What I check before moving WordPress to PHP 8.6: plugin and extension compatibility, Redis formats, OPcache memory, background jobs and a tested rollback.
What preparing my plugins for WordPress.org review changed
Preparing my plugins for WordPress.org review changed how they handle protected content, permissions, uploads and outside services.
One WordPress command centre that every plugin reports to
A WordPress command centre where every plugin contributes one card, and every card says where its figures came from and when they were true.
Managing a news aggregator's sources without slowing the site down
A publisher directory that took 174 MB, a cache stampede, adding outlets with a way back and retiring stale stories without deleting them.
Turning live sports data into pages people and search engines can use
Odds, a multi-source sports calendar, a map and racing results as server-rendered pages with ages on every value, one address per view and one canonical tag.
How to contribute to WordPress and write a better plugin
A practical guide to WordPress and open source contributions: reproduce bugs, test patches, review well and build plugins people can install and trust.
Four clock bugs that hide in scheduling code
Lost UTC offsets in British Summer Time, mismatched day buckets, drifting "last Friday" rules and midnight wraps: symptoms, tests and fixes.
Check-then-set is a race: atomic locks in WordPress
Get-then-set locks, dedupe and balances break under concurrency. Fix them with SET NX, wp_cache_add, GET_LOCK or a ledger, and test with parallel wp eval-file runs.
What a WordPress login lockout should actually do
Eight checks for a WordPress login lockout: count per account and per address, see the real IP behind Cloudflare, never reveal usernames, and never lock out the owner.
Test WordPress forms through to email delivery
Check the whole enquiry journey, from validation and confirmation to the right inbox, so a working form does not hide a broken handover.
Self-hosted WordPress: eight WP-CLI checks for speed and safety
Eight practical checks for WordPress on your own server: verify core files, run cron properly, find autoload bloat, lock down editing, use an object cache and update with a way back.
Move WordPress media off your server safely, then review its size
Plan WordPress media offload without broken images or exposed private files. Include CDN and backup costs, then measure before reducing server capacity.
Caching a WordPress block means keeping more than its HTML
A block can register scripts, styles and interactive state while it renders. I need those effects back on a cache hit too.
Cron, wp-admin and the front end need to agree where temporary data lives
A site can have a persistent object cache and still repeat the same remote calls if some request types quietly keep transients only in memory.
Check that scheduled WordPress jobs actually finish
Moving WordPress cron to a server timer can make the trigger more dependable. I still check the queue, the job’s progress and the result people see.
No guides match those filters. Try another topic or reset the filters.