Articles
Answers for your WordPress questions. Practical fixes, clearer workflows and new ways to get website work done.
Troubleshooting
19 articles · Clear filters
Problems with WordPress today and how to fix them
Most WordPress problems today are failures on one site. They are not a WordPress outage. The usual causes are a plugin update, a PHP fatal error, a cache serving an old copy or a limit set by the host. The quickest fix starts by finding the failing component, then changing one thing and repeating the exact action that failed.
· SiteSelf
Read article ›504 HTTP code on WordPress and how to fix it
A 504 means a server in front of WordPress waited for an answer and stopped waiting. It tells you where the wait ended, not why the work was slow. Find the request that timed out and the layer that cut it off, then fix the slow work or raise that one limit.
· SiteSelf
Read article ›Fix WordPress permalinks that are not working
When WordPress permalinks stop working, either WordPress’s stored rewrite rules are stale or the web server never passes the request to WordPress. Saving Settings → Permalinks fixes the first case in seconds. It does nothing for the second, and changing your URL structure to make the 404s go away usually creates a bigger problem.
· SiteSelf
Read article ›How to fix WordPress issues without guessing
Most WordPress problems end up on the same few screens: a critical error, a blank page, a 500, a spinner that never stops. The screen tells you something broke. It doesn’t tell you which layer broke, and the fix depends on finding that out from the logs and testing one change at a time.
· SiteSelf
Read article ›Why WordPress is not loading and how to fix it
“WordPress not loading” describes a symptom. It doesn’t tell you the cause. A blank page, a database error, a redirect loop and a domain that won’t resolve each fail in a different place, so each needs a different fix. Work from the outside in: first check who can see the failure, then read the exact message, then the logs. Change something only after that.
· SiteSelf
Read article ›Why WordPress updating failed and how to fix it
“Updating failed” is the name of two different problems: the block editor could not save a post, or WordPress could not install a core, plugin or theme update. Find out which one you have and read the exact error before you change anything. Most fixes are small. Most of the damage comes from the wrong fix.
· SiteSelf
Read article ›WordPress page not updating? How to find the cause
When a WordPress page won’t update, the edit has usually saved and a cache is still serving the old copy. WordPress core has no page cache of its own, so the purge buttons live in your caching plugin, your host panel, your CDN and your page builder. Clearing one of them while another keeps the old copy is the most common reason the fix doesn’t work.
· SiteSelf
Read article ›WordPress security issues and how to fix them
Most WordPress security issues start in plugins, weak logins and neglected maintenance, not in WordPress core. Before you treat an error as a hack, rule out an ordinary bug. If it is a hack, the fix is a full recovery, because removing the files you can see usually leads to the site being reinfected.
· SiteSelf
Read article ›How to fix a 503 error on WordPress
A 503 on WordPress means the server, or something in front of it, could not handle the request at that moment. It does not tell you which part failed. Work out which layer sent it before you change anything, because the fix for a plugin fault has nothing in common with the fix for a host limit.
· SiteSelf
Read article ›How to fix a WordPress fatal error
A WordPress fatal error means PHP stopped partway through a request. The “critical error” screen looks the same whatever caused it, so the fix depends on the error line in the recovery email or the PHP log. Read that line first, then make one change you can undo.
· SiteSelf
Read article ›How to fix SSL handshake failed on WordPress
On a WordPress site, “SSL handshake failed” can mean at least three different failures, and each one has a different owner. Before you change any setting, work out which connection broke: Cloudflare to your server, WordPress to an outside service, or a visitor’s browser to your site.
· SiteSelf
Read article ›WordPress login is not working? Fix it by symptom
A broken WordPress login is usually one of two problems. Either WordPress rejects your username and password, or it accepts them and sends you straight back to the login form. A password reset fixes the first one and does nothing for the second, so find out which one you have before you change anything.
· SiteSelf
Read article ›
Give your WordPress site its first task.
Connect the site you already have, add your agent to Slack or Telegram, and tell it what you need.
Start with 500 free credits. No credit card needed.