WordPress and Blackbird Pie: “There was a problem connecting to Twitter”

I have been using WordPress longer than a lot of people. I think I first moved from Windows Live’s blogging platform to WordPress around 2007. Because I’ve been here a long time, I’ve got some plugins that have been around for a long time. One of those is the Twitter Blackbird Pie WordPress Plugin.

The Blackbird Pie plugin was great when it came out. It let you use an embed code to add a live tweet directly into a post. It looked something like this:

[blackbirdpie id=”507693704581500928″]

The id was the unique id for one individual tweet. Twitter was just getting popular and this seemed really cool.

Later, Blackbird Pie got smarter and you could just give it the URL for the tweet on Twitter’s site.

[blackbirdpie url=”http://twitter.com/sympmarc/status/507693704581500928″]

The WordPress crew noticed the Blackbird Pie plugin and they even added it to WordPress in 2010. Instead of using the [blackbirdpie] embed code, you could just drop the url directly into your post. But dang it, it still wasn’t working for me.

I assumed the problem was that Twitter kept changing their interface and APIs and Blackbird Pie stopped working, regardless how you used it. For probably a couple of years now, all my Blackbird Pie -enabled tweet links have been broken. Each one has been showing the message “There was a problem connecting to Twitter”.

I’ve tried quite a few times to fix this, but I’ve gotten nowhere. All of the forum posts out there say things like “It was such a great plugin. Why doesn’t it work anymore?” The owner of the plugin seemed to give up on it, too.

WordPress 4.0 “Benny” came out today and I immediately upgraded, as I am want to do. One of the things I noticed in the release notes was that Twitter embeds are supposed to just work natively. “Well, why haven’t they been working on my site?”, I asked myself.

I don’t know why it occurred to me to do it, but I decided to uninstall the Blackbird Pie plugin. Presto, change-o, all was right with the world. Well, with tweets embedded in my test post. The problem was the Blackbird Pie plugin itself!

You can fix this on your blog by searching for all of the Blackbird Pie embed codes and switching to plain old WordPress embeds.

  • Go to Plugins and Deactivate and/or Deletel the Blackbird Pie plugin
  • Search for all of your posts with the [blackbirdpie] embed code by going to http://YourWordPressBlog/wp-admin/edit.php?s=blackbird
  • For each of those posts, edit it and copy the url to the tweet
  • Delete the embed code line
  • Paste the tweet url into your post

That should do it!

Moving My Blog from WordPress.com to Hosted WordPress.org

I’ve been thinking about moving my blog from WordPress.com to some sort of hosted environment running WordPress.org’s version of WordPress for a while. With all of the jQuery and CSS stuff that I do and other possibilities for customization and monetization, it just makes a lot of sense for me to have more control over my own blog. I’ve loved using WordPress.com and their platform is generally fantastic; I’ve just outgrown it.

It ought to be pretty easy to do a move like this, at least in my limited view of the world. As it turned out, some parts are relatively easy, but other parts are abysmally unclear or just plain don’t work. I figured I’d document some of the thornier bits in case other might want to go down this road. I think I’m a pretty savvy guy, but I ran into some really annoying or undocumented (at least that I could find) things.

WordPress.com’s site has some instructions that make all of this sound pretty easy. I mean, it’s computer stuff. How hard can it be, right?

First off, exporting the content from my existing blog just plain didn’t work with IE8. I’ve known for a while now that the WordPress platform doesn’t work well with IE, but IE is my default browser because it’s what most of my client work with. I’m sort of a Microsoft guy.

I kept trying to run the export and was getting errors. I fiddled and fiddled, looking at the XML coming out, tweaking values, etc. For instance, as you can see below, the XML seemed to be malformed. so I tried deleting the offending tags, etc., but to no avail.


On a whim, I tried doing the export in Firefox, and it worked fine. On the first try. Once I did the export with Firefox, I had a good XML file so that I could do an import on the other end.

Lesson one: WordPress likes Firefox better than Internet Explorer.

I think that is probably a safe statement across the board. There are certainly odd behaviors in the online editor in WordPress with IE, and that’s probably one of the main reasons why so many of us Microsoft folks use Windows Live Writer instead.

I chose HostGator for my hosting company. They are on WordPress.com’s preferred list, my pal Bjorn (@furuknap) recommended them, and they are cheap. Well, everyone’s cheap these days, really. But HostGator has a 20% off thing going, and I love cheap that’s even cheaper.

When I was setting things up up at HostGator, the site asked for my domain name. I didn’t think much of that, but it turned out to be a problem. The issue was that once everything was up and running and I installed WordPress (That install was fairly painless – sort of the promised single button click, except for the other 6 fields you had to fill out next without any real explanation. I guess every process starts with the “one button click”.), anything I did in the HostGator environment was linking me over to the WordPress.com “production” version of my blog – the old one. More fiddling, and I finally started a chat session with someone at HostGator. They were really helpful, but these aren’t the technologies I focus on, so some of it was Greek to me. It’s not that I couldn’t figure it out, but was it worth it? The mumbo-jumbo was different than my usual mumbo-jumbo.

Lesson two: Just because you know one set of technologies well doesn’t mean that you know all of them.

This may be obvious, reader, but don’t tell me that you haven’t tried to build a server or something you really shouldn’t have done. Maybe it’s that “man thing”; asking for directions is actually OK.

What the helpful guy/gal (sometimes it’s impossible to know in a teeny chat window with foreign names – should I have asked?) ended up doing was setting up temporary URLs for my new HostGator blog site. They would need to switch it back later, but that was supposed to allow me to move forward.

Lesson three: Maybe you shouldn’t believe *everything* you hear from an expert.

Not that s/he was wrong, necessarily, but it didn’t fix everything.

There were a few more chat sessions at this point to find out passwords and such, but they weren’t significant. Let it suffice to say that the UI behind the marketing screens don’t follow through at HostGator any more than they do anywhere else.

Lesson four: When marketing says something will be easy, we all know we shouldn’t believe that.

BUT WE STILL DO. What’s wrong with us?

The next step was to do the actual import of the XML file. The import kept just stopping with no errors, warnings, or messages of any kind. But when I looked at the setup, I would see all my posts – through December 2007, or March 2008, or…  Back to Bing, where the posts I found said basically, it will time out and you just need to keep running the import over and over until everything is there. What? Could that be true? Every time I ran the import after the first instance, all sort of errors flew by on the screen. The posts said that was OK, so I kept going.

Lesson five: Sometimes something which just looks totally wrong is supposed to be right?

I’m not so sure about this one.

After eight or ten imports (or more – I didn’t count well enough), everything looked like it *might* be there. The errors from the last few imports looked worse and worse, but they were “OK”, right?

At this point, I had my blog up and running with the temp URLs in the new environment at HostGator. I don’t like to trust technology too much, so I started to compare what I currently had on my blog with what I now had ion my new blog. You know, comparing counts of things, how the theme was applied, seeing what was missing, etc.

Lesson six: *Always* check your work.

There were still some problems that gave me pause. I’ve got over 600 posts on my blog with over 2500 comments and 500+ tags (I know, too many tags, but there you go). There’s far too much there to check everything; all I can do is spot check, really.

Here were my big concerns after more fiddling:

The Post counts on my Tags were all set to zero after import. In the grand scheme of things, maybe this isn’t so important, but I sort of like the Tag Cloud widget. Since all the post counts were zero, the tag cloud was uniquely uninteresting. Singularities are only interesting to physicists. I’m guessing that there’s some script I could run to fix this up (though it should be right from the import, IMO).

On my current blog, I use sourcecode tags supported by the SyntaxHighlighter Evolved plugin to embed source code. I’d like to continue using this plugin, as I find it makes the code snippets the most useful compared to any other approach I’ve seen. My blog is mainly about technology, and it contains a lot of code snippets; they have to be usable or what’s the point? The issue is that the code snippets in my existing posts seem to have gone across encoded. So rather than seeing this:


I was seeing this:


Another thing where some script probably would fix things up, but should I have needed to?

The comment count on my new blog was different than on my existing blog. As I mentioned, when I did the import, I had to run it probably eight or more times to get everything imported. On every run after the first, I got all sorts of errors, but it *seemed* like most everything moved over. The posts I read said this was “normal”, but since the comment count was different, I wondered what else might be out of whack.

Old blog:


New blog:


That didn’t seem right to me. Since there were all of those odd errors and the numbers didn’t match, I had no idea what the mismatch was caused by. And the new blog had *more* comments than the old one. How could that make sense?

All this trouble seems so unnecessary! It would seem that when there is an offer of an export/import capability, it should just work. Because I was using WordPress.com, I *couldn’t* do any wacky customizations; all instances there should be vanilla to a large degree, if not totally.

So after about four hours (or more; I should have kept track), I’m tossing in the towel. I don’t want to spend so much time on a one-time activity. I’m hiring the WordPress Happiness Engineers to do a Guided Transfer for me.

Final lesson: It doesn’t always make sense to learn how to do something if you are pretty sure you are only going to do it once.

I’ll probably never move my blog from one platform to another again, or at least I won’t do it again for a long time. It’s should be truly worth the $119 I’m going to pay Automattic | WordPress.com to do the work for me. (I sincerely hope that’ll turn out to be true; you’ll hear about it in this space if it isn’t.)

p.s. Thanks to Josh McCarty and Bjorn Furuknap for their support and suggestions along the way in this process. I hope the two of you don’t think less of me for hiring the Happiness Engineers.

Tweeting Old Blog Posts: Useful or Annoying?

Image representing Twitter as depicted in Crun...

Image via CrunchBase

Today I asked a question on Twitter that I’d like to also ask here so that I can get longer replies (if anyone has one). Recently, I realized that some of my old blog posts get questions or comments that (at least to me) tend to be interesting and/or useful. So I figured I’d start tweeting links to posts that were getting the attention.

However, it occurred to me that it could be annoying to people to get those old links cluttering up their Twitter stream, so I asked:


(BTW, showing the tweet above is my first attempt at using the new Bring Tweets To Your Content method recently rolled out by WordPress using Twitter BlackBird Pie. Very cool.)

I got several responses, which basically all said “Useful, but tell us why you are tweeting it.” Some were sent by DM, but here are a couple of the public ones:



What do you think?

SharePoint 2010 Theme for WordPress

I got an interesting email today.

I work with a company called Portal Front Hosting, a dedicated SharePoint hosting provider, and we have a new WordPress theme that is free to download and is inspired by SharePoint 2010. The link to a preview and download the theme can be found here: http://wordpress.org/extend/themes/sharepointforwordpress. Since you discuss SharePoint on your blog, would you consider sharing some information about our theme there? If not, any feedback about it would be great as well. Also, feel free to contact me by e-mail if you have any questions or concerns.

I emailed back and assured Heather that I would indeed mention this on my blog. I use hosted WordPress, so I couldn’t use the theme if I wanted to, but I’m sure there are some of you out there who might want to. I would think that most SharePoint people who use WordPress for blogging probably *don’t* want their blogs to look like SharePoint!


New Styling for My Blog

If you are visiting for the first time in a while, yes, you are in the right place.  WordPress came out with the new Neutra theme yesterday, and I decided that it was time for a facelift.  I tried changing the theme once before, and ended up backing off on the change. This time, I think I’ll stick with it.

I like this Neutra theme becuase it’s very clean and gets me back to dark text on a white background rather than the white text on dark background that I’ve had for the last year or more.   In all that time, I had one complaint about the color scheme and one atta boy, so there wasn’t a compelling user-driven reason to switch.  However, with all of the posts I do which contain graphics, generally best viewed on a white background, it seemed like this type of theme would work better.

So, welcome to the new look, and let me know what you think!