As it looks like there’s going to be a federal election in the near future for the Harper Government Government of Canada, I’m going to be contributing to the resurrected Carnival of Wank, a defunct-and-now-alive-again blog I contributed to once-upon-a-time. I think it’s better to keep my politics mostly away from this site (side from the Pirate Party logo over on the right of the page) and focus on technical posts, so if you want to read up a little on the Gong Show that is Canadian Politics, head over to CoW.
« Posts tagged Meta
Rant: WordPress.com Stats Broken, Makes Me Sad
Update: WordPress.com finally fixed the Stats issue, however Jetpack (despite the version bump to 1.1.1) still errors out, this time with “register_http_request_failed“.The issue appears to be with LigHTTPD, as if I switch back to Apache everything works. Might finally break down and switch to NGINX, as Apache is too big of a memory hog for my liking.
The other day, the WordPress.com Stats plugin I use to spy on you monitor this blog stopped working. Then I started getting this error from Stats:
Your WordPress.com account [Redacted] is not authorized to view the stats of this blog. Currently access to stats is broken for some users and we are working on fixing this. Your stats are still being counted and will be visible once we restore access for your account.
Fair enough. I waited. And waited. And waited some more. When it became apparent that this wasn’t a temporary problem, I removed and re-added the plugin, and was then greeted with this new, more exciting error:
“The owner of that API Key ([Redacted]) is not on the access list for this blog ([Redacted]). Stats was installed using a different API key. The owner of the original key can add users to the access list, or you can contact WordPress.com support.”
Huh. Well, since that didn’t do it, I did some Google’ing and found out that Automattic just released Jetpack, a collection of plugins that replaces a good chunk of the standalone plugins out there that work with WordPress.com services. People who were getting the above errors reported that the Stats plugin provided with Jetpack worked, so I switched. And immediately received yet another error:
Your Jetpack has a glitch. Connecting this site with WordPress.com is not possible. This usually means your site is not publicly accessible (localhost).
Fantastic. Google once again helped me to find a bunch of other users with the same problem, but sadly, none of the fixes (most of them found in this thread) worked for me. I broke down and contacted Automattic support, and their reply was the following:
It might be the SSL cert that is preventing Jetpack from connecting. Is the site also behind any sort of firewall?
Which, of course, the site is. However, that was the first thing I checked, as my IPTABLES rules are just north of Insanely Restrictive. Sadly, disabling IPTABLES did nothing to help. Additionally, I was able to confirm that outbound SSL access was working by using CURL from an SSH session to grab pages from https://wordpress.com, so that’s not the issue either. I replied back to let him know this, and I’m waiting on a response. Through all of this, the normal WordPress.com Stats Plugin still doesn’t work. So,
My new favourite meme.
Fixed: Broken Permalinks in WordPress
I recently moved servers to a new host (a friend of mine had provided me with a free CPanel account on his VPS before this), and the transition had appeared to work rather well. Then, when I checked my blog stats this morning, something seemed off:
See that last big dip? Guess when that happened!
So I started looking around the site, and sure enough – the main pages displayed fine, however everything else was broken. In fact, anything with a ‘fancy’ permalink was 404′ing.
Once again, a quick Google search lead me to this thread on the WordPress forums. After digging around, I found the problem – in Apache’s httpd.conf file on my new VPS, I needed to change the following line:
AllowOverride None needed to be AllowOverride All
Note, though, that there are two AllowOverride entries in httpd.conf – one wrapped in <Directory></Directory> tags, and one all by itself. The problematic one is the second AllowOverride entry that isn’t wrapped in Directory tags.
TL;DR Version: If you enable fancy permalinks in WordPress, and start getting 404 errors in Apache even with a proper .htaccess file and mod_rewrite enabled, change AllowOverride None to AllowOverride All in httpd.conf – just make sure you do it to the second AllowOverride entry!
Updated! If you’re using nginx instead of Apache, simply add the following to the location section of your nginx.conf file (or the one for your vhost, if you’re doing that):
if (!-e $request_filename) { rewrite ^.*$ /index.php last;}
Updated again! If you’re using ligHTTPD, you can add the following line to lighttpd.conf (although if you are using your own custom 404 error page, you may wish to find another solution):
server.error-handler-404 = "/index.php"
Meta: Comment Spam Funnies
I’ve been getting a fair amount of spam in the comments, but Akismet has done a pretty good job of flagging them for review. I decided to start collecting some of the funnier ‘comments’, because I really can’t believe that people actually get paid to do this (and then do it this badly). For those not in the know, spammers frequently get paid to leave ‘real’ comments on blogs, and link to the target website. It generally makes separating the signal from the noise rather difficult when trying determine if something is spam or not, however in the case of these comments, it’s pretty clear what the intention is.
Here are the best of the worst:
Took me era to scan all the comments, but I extraordinarily enjoyed the article. It proved to be Extremely sympathetic to me and I am satisfied to all the commenters here! It’s each time delightful when you can not no greater than be informed, but also entertained! I’m stable you had rag theme this article.
Just write like you’re talking to your friends. And soon, they will be
I was looking during momentous information on this subject. The advice was consequential as I am wide to set up my own portal. Thanks for providing a missing relationship in my business.
Me and my friend were arguing yon an issue similar to this! In the present circumstances I skilled in that I was right. lol! Thanks in favour of the data you post.
Curt Schilling I am so tired of your self righteous preachings. Talking about how Manny didnt try and how shameful that was. Did you ever say anything about how you conned the Red Sox into an 8 million dollar deal and then revealed you were injured and didn’t throw a pitch all of this year. Stop judging other people and worry about yourself you seem to know whats best for everyone but yourself
Hello there, anyway i mearly thought i post and let you be aware your site design has been significantly nice
Resources like the bromide you mentioned here will be absolutely gainful to me! I will enter a concatenate to this page on my blog. I am sure my visitors choice get that greatly useful.
Easily, the article is really the sweetest on this worthy topic. I agree with your conclusions and will thirstily look forward to your coming updates. Just saying thanks will not just be enough, for the wonderful lucidity in your writing. I will right away grab your rss feed to stay abreast of any updates. Admirable work and much success in your business enterprize!
I think my favorite is the second from last – I guess I need an article that talks about Bromide? Does this count?
