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.

So, there it is. TextMate 2 Alpha support. If you notice anything weird please open a Support Ticket on GitHub. Please include the full text of the error that you receive as that’ll most likely be what I need to fix the problem.

WordPress 3.3 support is hot on its heels. Really!

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.

Without an Apple computer company backed by Steve there’s a good chance that I wouldn’t be doing what I’m doing, where I’m doing it, and would have missed out on some very influential relationships in my life. So I’ll keep this short.

Thank you, Steve.

I just merged a pull request from Simon Wheatley in to the WordPress TextMate Bundle that adds the command wpsalts to generate the Security Keys for the WP Config file. The command uses the WordPress.org secret-key Service.

Very handy.

Thanks Simon!

In case you’ve noticed the amazement lately on blogs and twitter where BBEdit users have discovered a way to open a curl’d url in BBEdit to view its source you may be wondering “how do I do this in TextMate”?

Well, its a little more code, but its also a little more powerful.

So, add this as a command in your bundle and tell it to open a new document when its done. Assign it to a keyboard command (if you haven’t already assigned other items to every other keyboard combination under the sun like I have). From here you can simply highlight a URL in a document, trigger the command, and get the source of the url in a new document.

On top of that, if the url contains credentials a-la “user:password@http://foo.com” it’ll use the “user:password” portion to authenticate you against simple Apache 401 authentication.

I’ve been thinking that it would be nice to have this also check the clipboard if there’s nothing selected. But I haven’t gotten around to trying that yet.

This and a few more helpful commands can be found in my General TextMate Bundle on Github (also available through GetBundles).

Enjoy!

After much fiddling, the updated WordPress TextMate Bundle is here and it has been updated with a much better function definition display. I’ve ditched the old function scraper that was an abomination of grep & regex matches and replaced it with doxygen and some ruby abomination to provide much more information about the function or method being inspected.

I’m pretty sure there’s a lingering issue with the parsing and display of special characters in the doxygen output (which I blame squarely on strange handling by doxygen) that I haven’t handled yet. There may be HTML Entities missing from the documentation here and there.

Also improved is that the function definition search is contextually sensitive. It’ll only look for methods when in object scope (ie: $object->method();) and only look for functions when in regular php scope (ie: function();). There’s also a prompt to select the method that you’re actually after when multiple matches are found.

So, as always there’s something that can be improved upon with the bundle, but its moving forward and getting better with each revision. I guess that’s something, right? RIGHT?

So, fire up GetBundles or head on over to the WordPress TextMate Bundle’s Github Page to update your bundle!

Enjoy!

Despite how simple it is, I could never remember the sed command to remove a line from a file. To help get around having to repeatedly manage my known_hosts file and/or look up the sed command I wrote a little function to remove lines from files using sed. Hopefully someone else out there finds this useful.

So, stick that in your .profile and smoke it enjoy!

While enabling these caching settings is good for performance they’re not really good for development since both filesystem paths and interpreted code can be cached for periods of time. What made me notice was when a machine here in the office wasn’t honoring the new path to a renamed folder. The assets in this folder were all loaded via include statements using relative paths. Hard coded paths should not have been an issue, but for some reason the system kept looking for the files in their old location.

It took a while before I narrowed it down to the caching settings as a culprit. Once we turned off caching all together our changes were reflected immediately and all was right again with the world.

What you need to do

The modification is simple, its just a change to the MAMP preferences.

1. Open MAMP
2. Click the “Preferences” button or select “Preferences” from the MAMP menu
3. Click on “PHP” in the tab-bar if its not already selected
4. Change the “Cache” dropdown to be “––” so that no caching extension is used
5. Click “OK” to save the changes
6. Restart MAMP (click “Stop Servers” and then “Start Servers” once they’ve stopped)