I’ve been out of the WordPress loop for a little while now and I’m not up to speed to what some of the new developer oriented hotness is that could be added to the bundle so if you’re looking for something in particular drop a comment here or open an issue on GitHub.

If you’re so inclined go ahead and Fork it, update what you need and submit a pull request. Since I don’t work with WordPress on a regular basis there are going to be those of you out there that have a better grasp than I on what should be added, or even what should be removed, from the Bundle.

So, my apologies for the delay with the update. I’ll try not to let it happen again.

I’ve been doing some cursory testing with the WordPress Bundle and so far it appears that only a few minor modifications might be needed to be compatible.

Better yet, though I haven’t fully tested this yet, the changes should be backwards compatible with TextMate 1.5. For the time being it doesn’t appear as thought I’ll have to create a branch just for TextMate 2.

So, keeping in mind that TM2 is Alpha, I’m pleased with how things are panning out. I’m eager to get in to the guts the new bundles and figure out what more I can do to make the WordPress bundle even better (suggestions are welcome!).

Congratulations to Mr. Odgaard on his release. I hope he’s able to ignore the petty jerks who keep harassing him and finish up what already looks to be a kick-ass upgrade.

No new features have been added yet, but this will at least jump you to the right place in the code base when needing to inspect an internal function. Suggestions for feature additions are always welcome, so lemme know how you use the bundle and how any improvements can help you use it better and I’ll see what I can do. As it always has been, the project’s source is freely available so you’re welcome to contribute as well if you wanna dive in to a little bit of Ruby code.

I know I’ll regret saying this, but one of my goals to hit during the 3.1 lifespan is a better code scrape of the WordPress core. I’ve been playing with a couple of different code scrapers/documentation engines to replace the janky regex that I’ve got going on, so hopefully I can find the time to put in to this as I think getting as much of the built in documentation to the surface as possible would be a boon to my sanity. Maybe once I’m caught up on my hackers list reading (I think I’m about 3 months behind) I might have a couple of ideas for adding to the bundle

Cron/Scheduled Events

I’ve never really worked with the built in Cron in WordPress but have heard others talk about how much of a pain it is. After recently reading a Sitepoint.com article on scheduling events I was able to get the jist of it. The WordPress Bundle now includes snippets for complete actions such as registering single and recurring events. I figure I had better get the snippets in there while it was fresh in my mind.

Transients

A little less fresh in my mind were Transients. After watching a presentation on caching at WordCamp Boulder by the very likable (and, yes, smart) Sean O’Shaughnessy and Chris Scott from Voce Communications I got pretty stoked about these functions. Like the wp_cache… shortcuts there are now shortcuts to the transients functions. For more information about the wonderful world of transients check out WordPress Codex pages on the Transients API.

Scripts & Styles

Two new shortcuts for wp_register_script and wp_register_style were added. Though they’re a couple lesser used functions, I feel they’re a bit underused as well.

All done for now

So, while not a huge update it adds some obscure references that hopefully help some folks dive deeper in to developing for WordPress.

The bundle had been updated to support the new features in WordPress 3.0 including, but not limited to: custom post types, featured images, and WordPress MU integration. The menu has been rearranged a little bit and a slew of new commands and snippets have been added. Hopefully, :knock-on-wood:, no bugs have crept in.

So, go and get WordPress 3.0 and update your WordPress TextMate Bundle!

The goal of adding this support was to make it as seamless as possible to integrate with your coding style. The command will properly adjust itself for whether your selected text is within a single or double quoted string, it is a quoted string itself, or if it is in a block of HTML instead of PHP.

The command is found under the “Plugin API” section of the plugins menu or by using the command-shift-i keyboard shortcut.

Inside Single and Double Quoted Strings

With the sample code:

Selecting text “two three” WITHIN the quoted strings will return:

Single and Double Quoted Strings

Again, with the same sample code:

Selecting the entire quoted string, including the quotes, will return:

Inside an HTML scope

Here our code will return a bit different. With this as our example:

Selecting the string “one two three four” will return:

Here it uses the _e() (echoes the result) function instead of the __() (returns the result) function.

And there it is…

So, overall not complicated but super duper handy. I can’t believe that I didn’t think about this earlier. It was just suggested by Mr. Gordon Brander earlier today and I was so giddy to get it implemented here I am on a Friday night getting it worked in!

Version 1.2 adds support for Custom Post Types and allows the token functionality to be enabled or disabled for Posts and Pages. In WordPress 3.0 this will also allow custom configuration of the newly exposed Custom Post Types as well (pending that you’re using that feature). Simply select which post types you want the plugin to work on in the Settings page.

This version also fixes a couple of security issues. First: The settings page has been hardened against the possibility of Cross Site Scripting Forgeries. Not that it was a huge deal before since this plugin doesn’t advertise itself on your blog in any way, but its nice to know that we’re protected. Second: The settings page in the admin is not exposed to users who do not have the privilege to manage-options. The settings page wouldn’t display for these users before but the menu item was still there. Now the plugin doesn’t expose itself at all to users who don’t have the privileges to use it.

Version 1.2 supports the upcoming WordPress 3.0 release and deprecates support for WordPress versions earlier than 2.8. It probably still works on 2.6 & 2.7 but, frankly, I don’t want to test on those versions any more.

Lastly, and this was a change that I actually snuck in with the last minor release, support is now being handled through The WordPress Help Center (the PPT page on WPHC). The WordPress Help Center is pretty much a one stop shop for troubleshooting any issues you may have with using or managing your WordPress install and can also be hired on for small design and development tasks. Give ‘em a look see. I bet you’ll like them .

Thanks to the guys (and gals?) over at Bare Bones my WordPress Clippings for BBEdit are now listed on the Official BBEdit Clippings Library page.

Now I’ll have to see if I can talk them in to some kind of developer discount as I haven’t had a chance to test newer versions of the Clippings since my trial ran out.

There wasn’t a lot that changed as far as the bundle is concerned, most of it being about a shift in line numbers of where the functions are located in the core so that the Jump to Function action works properly. There’s also a built in About page now that provides documentation on the plugin as well as credits to the folks who have helped out.

The versions of the Bundle and Clippings that are compatible with WordPress 2.8 have been tagged at GitHub, so they’re still available through a direct download or git checkout.

On a side note, a less used (and maybe less practical resource), my WordPress Hooks Tag Cloud has been updated for the new 2.9 version (and, 2.8… whoopsie!). If you’re looking to see where a certain action or filter is used you can find that out there.

Also as of this release the old GitHub project repository is officially deprecated. It will be coming down soon, so direct any support requests to the contact page on this site. Thanks!

You can download the new version here.

Enjoy!