Bit by Bitly!

A bizarre bug in a Firefox plugin pretty much 86ed this blog for anyone using IE in the last month or so. I installed the Bitly Preview Firefox plug-in, which expands shortened urls in web pages so you can see where they’ll take you. Seemed useful, since I’m active on Twitter and they show up there all the time.

Anyway, this plugin apparently had a bug. If you had the 1.1 version installed, and you edited anything in a rich text editor (like, um, the one I’m writing this post in), it would toss a little javascript code in after your text. The code wasn’t malicious – it was pretty ineffectual – but Microsoft’s Internet Explorer, versions 6 and 7, were completely dumbfounded by it (MS admits that this is a bug and say that they’ve fixed it in IE8). Anyone visiting the blog in those browsers recently has been hit with a pop-up error complaining that the page can’t be displayed. This blog is not the biggest destination site on the web, and I’m pretty sure that most of you are reading this in the comfort of your own RSS reader (you should be – look for my upcoming Idealware article explaining how and why, if you aren’t).

Anyway, the fix was to remove or upgrade the bitly plugin; load up PHPMyAdmin on my server and run the query:

select * from wp_posts where post_content like ‘%bitly%’;

then, since I only had a handful of matches (my last five posts), select them all and remove the line at the bottom of each post, which was a script containing the text:

Definitely one of the odder glitches I’ve experienced!

Share Button

6 thoughts on “Bit by Bitly!

    1. Peter Campbell Post author

      I found the javascript, which referred to bitly, in my blog posts (view source), and since I didn’t have any plugins running that would put something like that there, I googled it. I found a comment on Friendfeed linking to a post that gave me enough info to work it out from there. I did note that other people were having tehs ame problem, and hope they’re finding my post when they google it.

  1. Tim McGovern

    I found your post after I identified the source of the error. If you’re interested, adding the specific error message IE generates would likely draw more people to the post. I know that is the first thing I googled. Alternatively, adding comments to some of the top SERPs for that error would likely be helpful.

  2. Tim McGovern

    Search Engine Results Page — essentially the set of results you get when you search for something.

    My first search was for “operation aborted error ie”. Each included an explanation of the error, but adding a specific potential cause might be helpful.

    No worries if you think it doesn’t make sense.

Comments are closed.