Skip to content

Twitter Player Card for Blubrry PowerPress WordPress Plugin

Dear Reader,

For the past 10 years I have been a podcaster. In that time I’ve used a lot of tools to present my podcast. None of them are better than WordPress and PowerPress. The one thing that PowerPress is lacking is the ability to create a Twitter Player Card for my content. So I hacked something together.

PowerPress Player Card is a WordPress plugin. You have to have PowerPress installed and activated before it will activate. Without PowerPress, it’s useless anyhow.

The Readme contains installation instructions. You have to install it manually because it isn’t in the WordPRess plugin repo and most likely never will be.

Once you have it configured and you’ve validated your card using the Twitter Card Validator, everything is automatic. Add your podcast post and when the link is tweeted, users will see the player, right in their page.


Screen capture of a twitter player card for Voices of the ElePHPant
So now casual listeners can enjoy your podcast without having to subscribe to your feed or get a podcast app.

Thank you BluBrry for a great plugin.

Until next time
I <3 |<


The Rejection by Andreas WintererDear Reader,

One of the biggest complaints I hear about WordPress is that yes, you can choose from thousands of plugins, but many of them are crap. Because there was no barrier to entry, many of them were poorly coded and could even introduce security vulnerabilities to your site. I recently found out the hard way that WordPress is moving to change that. :)

First, they have been retiring old and unmaintained plugins for a while now. Thankfully, that includes all the plugins I wrote back in the 1.5-1.9 days. :) More importantly though, there is now a code review before accepting new plugins. This is a very good move on their part and I applaud them for this move.

There is a small problem though. They don’t seem to have published anything on what is acceptable/unacceptable in a plugin. In discussing my particular plugin with the reviewer, it seems the rules are kind of fuzzy as to what gets accepted or not, and they seem to be changing.

Overall, I think that a code review process is a very positive move for the WordPress ecosystem. It would be nice however, if the review team published the current rules. Even if those rules change, a current set of rules would help make sure that plugin developers don’t waste time and effort on plugins that won’t be accepted.

If these guidelines are already available, linking to them from “Writing a Plugin” would be apprecaited.

Well done, WordPress!

Until next time,
I <3 |< =C= p.s. I am working on updating my plugin to change the reported problem so that hopefully it will be accepted next time. (fingers crossed) :) Photo Credit: The Rejection by Andreas Winterer. Used under Creative Commons License.

Odds and Ends

Dear Reader,

Yes, I’m still alive and no I’ve not taken to just shoveling up the crap the “devzone”: turns down. I’ll return to blogging soon and even to “blogblinging”: But here’s what’s up right now.

The company I was working for is in a bit of a financial pickle. I’ve picked up a short-term contract doing some super-secret cool stuff but it’s not permanent. So if you know of anyone looking for someone to take their development team to the next level, send them my way. “Obligatory link to my resume”: I have a lead on something permanent if this contract goes well but I don’t have a feel for that yet so I don’t want to jinx it.

I’ve been working a lot in “AJAX”: for the past couple of days using the “YAHOO library”: I must say that it is an impressive if large piece of code. I’ve been using the “dragdrop”: portion of the code and am really liking what I see. It’s not as ‘user friendly’ as “”: but it’s much more powerful. I started this project in “”: but had to abandon it because I couldn’t get the fine-grain control I needed. Basically, IMHO, “”: is great if you are looking to Web 2.0-erize your site but if you are building a serious application, you are going to need “YAHOO library”: When I finish I’ll blog togehter a little tutorial about what I learned because a lot of what I’m learning I’m having to learn by reading other people’s code and keep trying different things till something works. (Old-school, cave-man coding)

Someone reported today a problem with “WP-Notable”: and “WordPress 1.5.1”: I don’t have a 1.5.x blog running anymore so I can’t test it. I know what the problem is but 1.5.1 doesn’t support the function I need to call. So for the moment, if you are running 1.5.x I highly recommend you use one of the other packages that do this. (No, I won’t point you to one, google around, you’ll find them.)

I’m working on my “tagcloud”: project. I’ve decided that it needs a second dimension. Right now size indicates popularity of the topic. (Well, it really depends on how you set your CSS) I also want to be able to imply a second dimension. In the test case I’m working on, I want to confer relative age of the topic. (Very popular but old isn’t interesting, kinda like George Clooney) I’ll be doing this by fading the color as the second dimension.

Anyhow, that is what’s up with Cal. Hope you’ve enjoyed it. Hey, in case you missed the memo, my weekly “Zend Framework Mailinglist”: Roundups now have their own tag. Check them out “here”:

Until next time,


Another “Notable” update

Dear Reader,

Yep, it’s that time again. Time to dive in, grab the new code and beat it into submission.

I’ve updated WP-NOTABLE, part of the BlogBling line of plugins. I fixed a problem where it would reset your options each time you went to the admin page. I’ve also implemented support for thanks to their support department sending me the code.

You can download from the Project Page. Complete (and hopefully user friendly) instructions are there as well.

Until next time,


BlogBling General Update

Dear Reader,

This is for all of you who use my blogbling plugins. I’m in the process of updating them all. I’ve updated WP-NOTABLE and WP-ESBN and WP-FATTER but the rest will be updated soon. The reason for the update is that it was pointed out to me that the plugins that ran in the_loop were causing a lot of hits on the database. I’m updating them all to be more database friendly.

Also, I’ve recently updated to WordPress 2.0.2 All plugins seem to be working fine. The only thing I had to do was check my ESBN options, for some reason, they did not survive the deactivate/Activate. I’ll look into that.

To the best of my knowledge all of the ones recently updates are now working correctly. Feel free to correct me on this.

Until next time,