I’ve LOLed over the most controversial function added to WordPress 3.0: The capital_P_dangit function. Basically, it forces WordPress to be spelled with a capital P, as decreed by Matt M and the other core developers.

Some people are angry that it is an arbitrary editorial control mechanism, so there’s been a huge fracas on the wp-hackers email list. Quite hilarious, actually, given the relatively small impact that the code itself has.

Lost amongst all of the brouhaha was John Bloch’s contribution on how to easily remove the filter:

remove_filter('the_content','capital_P_dangit');
remove_filter('the_title','capital_P_dangit');
remove_filter('comment_text','capital_P_dangit');

Simply add that code to your functions.php file and call it a day

Feeds are a wonderful thing. I love my Google reader, because I can keep up to date with all the new web designery goodness available on teh intarwebs.

Feeds are also useful as content sources for people too lazy to write their own stuff. I know, I know, it sounds awful to say it that way, but that’s the reality of it all. If you had awesome content bursting out of your own ears, you’d never need to pull in someone else’s finely wrought content.

Back to the point, this is how a trillion how-to tutorials on the web teach you to pull a feed into WordPress, serverside:
Continue reading

WordPress 3.0 final was released into the wild today, and guess what? I’m using it.

I’ve been using the WordPress 3.0 RC1, RC2, and RC3 for a while, using the WordPress Beta Tester plugin, and so far it’s been relatively painless. A few of the plugins weren’t working, which I stupidly forgot to note, so that I could pass it along to the plugin developers, but overall it has been very stable.

Who’s to say how much of a pain it’s going to cause me at work, given the proprietary nature of some of my company’s in-house developed plugins. We try to build things the “WordPress” way, so hopefully there are only a few minor hiccups.

As to security, I once again wish that WordPress would adopt a two-pronged release strategy. Yes, go ahead and release the latest, greatest bleeding edge version as your main release. But please, PLEASE, start a long-term-support (LTS) branch. Or not. Whatever.

The back-end is a touch cleaner, although I can’t exactly put my finger on all the changes, other than the color. (I suppose I could do a side-by-side, but that would be too easy, wouldn’t it.)

Long story short, I’m working on building some new theme templates that take advantage of the new menu system and a few of the other additions. It’s exciting finding a new theme function! (NERD!)