Below you'll find a list of all posts that have been tagged as “troubleshooting”
You have some spectacular ideas for your WordPress site that needs fixing, but you’re not a coder. So, you need the services of a professional WordPress developer or designer. But where to begin? There’s an entire World Wide Web vying for your attention with what seems like an endless supply of developers and designers raising their hands saying, “Pick me! …
Picture this: You’re working away on your WordPress site and then bam! You see this puzzling and face contorting error: “How is this even a thing?” you quietly shout. “I am allowed to access this page. I’m the admin!” The frustration continues when you realize the fix isn’t so cut and dry since there are multiple […]
There’s a WordPress error that’s frustrating to no end because if you’ve come across it, you probably didn’t actually do anything wrong. Still, plastered across your site will be these words: Warning: file_get_contents(path/to/wordpress/file): failed to open stream: No such file or directory in /path/to/another/wordpress/file.php on line # The error message itself is almost misleading because […]
So you’re clickity-clacking away on your keyboard, working on your WordPress website, when suddenly your sidebar appears below your content where it shouldn’t be. Worse still, there’s no clear error message. Zeus’ beard! What happened? Did your theme implode?? Before you get angry and rip your shirt off, Hulk-style, or tear your room apart in a […]
There’s a small group of befuddling errors that elbow themselves in, front and center, on your WordPress site, forcefully ripping it down from the world wide web: “Parse error: syntax error, unexpected…” “Notice: Use of undefined constant…” “Parse error: unexpected…” All you did was add a bit of code to adjust the look of your […]
When your website throws up a 403 error with “Forbidden” plastered across the top in imposing bold letters, it’s just a bit rude, right? I mean, it’s your website and you can’t access it. The nerve! I mean, you’re the site administrator or even the owner and your site has locked you out. Fortunately, troubleshooting and fixing this error so …
Here’s a frustrating yet common WordPress error that can appear out of the blue, bringing down your site in one fell swoop: “Warning: Cannot modify header information – headers already sent by (output started at…” What’s worse is that this error continues, listing paths to important files on your server which is a potential security risk. But not to worry! …
The vaguest WordPress error you’ll no doubt come across at some point, which also has a whole laundry list of probable causes, is… “Are you sure you want to do this?” What’s frustrating about this particular error is that it could mean you made a small fixable mistake or, worse, that you’ve been hacked (though typically it’s a security issue that’s …
The 500 Internal Server Error is one of the most common panic-inducing “I’ve broken everything!” catch-all errors in WordPress that can literally mean anything. The most common reasons for WordPress throwing up this error include having a corrupted .htaccess file, exceeding your PHP memory limit, or having improper file permissions, but there could also be other potential causes, such as …
Getting hacked is one of the most frustrating experiences you’ll face as a site admin. Unfortunately, even if you have bolstered your site’s defenses, about 30,000 sites are hacked daily and it’s likely your site will fall prey sooner or later. So it’s important you know what to do when that day comes. Fortunately, it’s possible to figure out exactly …
