- A few handy git aliases
- Operation Shave the Wookiee, the Return
- Art at Stanford
- A Winters Day at the Beach with the Fuji X-E1
- MacPorts, Homebrew and Mountain Lion
Polluting the internet since 2004
Here the posts under the “works” category will be gathered so that anything that could be considered “portfolio” material can be seen in one spot.
The Post Password Token Plugin has been updated for compatibility with WordPress version 3.4 and newer (tested up to 3.5 alpha).
In 3.4 the post-password cookie was updated to contain an encrypted value, something that was probably long overdue, and caused the PPT plugin to fail in authenticating the post.
All is well now. Update your plugins and enjoy!
FINALLY! WordPress 3.3 support is up for the TextMate Bundle. This is pretty much an update to the function definitions to add in new functions that were added in WordPress 3.3.
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.
We’re all excited to see that TextMate 2 Alpha has been released. It was a long wait but by the looks of the Alpha it appears that the wait wasn’t wasted. There’s plenty to be happy about with the Alpha.
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.
WordPress 3.1 RC is here, so I figure its time enough to issue an update my [recently neglected, sorry 'bout that, its been busy] WordPress TextMate Bundle. All function definitions have been updated to the 3.1 RC code base. There is a tag for the 3.0 branch as it sat this afternoon.
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
I just updated the WordPress TexMate Bundle with some new features.
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.
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.
Two new shortcuts for
wp_register_style were added. Though they’re a couple lesser used functions, I feel they’re a bit underused as well.
So, while not a huge update it adds some obscure references that hopefully help some folks dive deeper in to developing for WordPress.
Today marks the release of WordPress 3.0 and with this release the WordPress TextMate Bundle is ready for it.
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.
The WordPress TextMate Bundle was just updated to include support for internationalizing strings. Its not terribly obvious how the feature can be used, so I thought that I’d do a quick outline of its features.
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.
I’m happy to announce that version 1.2 of the Post Password Token plugin for WordPress is ready to go and available for download from the WordPress Plugin Library. If you already have it installed you just might have an upgrade notice on your plugins page.
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 .
Look, ma, we’re famous! Ok, not really.
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.
The Post Password Plugin plugin for WordPress has been updated to version 1.1. This new version adds a feature to hide all password protected posts from anything but direct access. With this option enabled password protected posts will not be pulled from the database unless the post is accessed directly. This allows for truly hidden posts that only you and the people you notify know about. This way your regular readers aren’t asking you why they can’t access certain posts and nobody knows that you’re posting items in secret.
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.
The Post Password Token Plugin for WordPress has been updated to version 1.0.2. This includes a minor bug fix for a permissions error when using the link from the plugins page to access the plugin options.
If you’re not experiencing issues there’s no immediate need to update. Accessing the plugin from the link in the WordPress Admin Sidebar works as expected. This in no way effects the functionality of the plugin.
This release also moves the plugin completely away from GitHub to reduce redundancy in hosting/versions.
This post is to introduce the WordPress Post Password plugin. This is a plugin designed to allow users to access password protected content without having to enter the password. This plugin was built based on an idea from, and in cooperation with, Gordon Brander.
The concept is simple: when a post is given a password the plugin will automatically generate a password token that when used in a URL will automatically log the user in to the post without them having to know or enter the password. So, in the event that you just want to keep the riff-raff out don’t care about “ultimate” security this plugin can help you distribute an easy to use URL instead of a URL & Password. The tokens are built based on the post’s password, so changing the post password will change the token. In the event that you need to reset all the tokens at once there’s a central “salt” that can be updated to force all the tokens to update.
You can read more and download the plugin at the Post Password Plugin’s page on WordPress.org.
This is version 1.0. We already have plans for version 1.5
As much as I’d like to jump whole hog on the PHP 5.3 bandwagon I just haven’t had the time to read up on the compatibility issues not work out what I’d need to do to maintain a PHP 5.2 and a PHP 5.3 environment on my computer. For now I’ll just be sticking with PHP 5.2.x.
This creates a problem, though, as MacPorts constantly lists my PHP 5.2 as outdated.
While I don’t want to upgrade to PHP 5.3 right away, I still want to have a quick and easy upgrade of everything else that I have installed. There’s not any clear documentation about excluding ports from a port command, but there is a tasty morsel in the
port man page.
These two have always been questions in my mind but until recently I’ve never had the need to actually put time in to satisfying my curiosity and as I look around I haven’t (easily) found any real world examples of these out there.
So, we all know how to set up basic HTTP authentication, right? Good. Here we go…
Maybe you noticed already, maybe you didn’t (I’ll wager on the latter ) that recently this site got new source code highlighting in posts. Or, should I say, that it GOT source code highlighting in posts.
I had made a simple Script Source viewer a while back. Something simple and straight forward that I could use to display full source code files in an easy to read and copy format (since the source is an ordered list the line numbers don’t copy). I was so happy with the way the source highlighting along with the line numbers turned out that I really wanted to put that in my posts. But I guess not wanted bad enough to do right away.
So, now I finally got around to putting this together for use inline in my posts and decided to package it together for public consumption. The highlighting is pretty durned nice and fully CSS configurable. It supports a decent number of languages and if it doesn’t support your language of choice, chances are there’s something in there that’s close enough.
The only drawback, and this may be a show stopper for some folks on shared hosting, is that it has a dependency on the Pear Text_Highlighter package. Since this plugin was primarily for me and I have control over my servers this isn’t a big deal here, but may keep some from being able to use it at all. If you like it enough then contact your host. You never know, they might be accommodating. There’s more about this on the project page. It basically boils down to: if you don’t know, it doesn’t hurt to ask.
So, enough already, head on over to the SP Source Code Highlighter Plugin’s Project page and see how it looks and works.
The WordPress TextMate bundle has been updated for WordPress 2.8. New items include:
Get more information on the WordPress TextMate Bundle project page, download it from the Github project page, or, if you installed it via GetBundles (which is really the best way to keep up with it) you can simply upgrade it from TextMate. If you don’t already use GetBundles, you really should. Use Subversion to install it from that url.
As the name implies this is a TextMate bundle to assist with WordPress development. Where I work we’re on WordPress almost every day doing this or that and it gets pretty tedious to not only remember the schizophrenia that is PHP syntax, but the schizophrenia that is my own code as well as the schizophrenia that is the WordPress code base (don’t take that the wrong way, pretty much every code base out there is a little bit schizo).
To that end I got together with my co-worker Gordon and started hacking together this bundle. Gordon’s a detailed oriented guy, and I like to pretend to be, so together we were able to sufficiently over-analyze the situation and put together what we feel is a heck of a good resource for developing under WordPress with TextMate (someone I know has already taken part of it and converted it to emacs! Heathen ).
So if you’re a TextMate user you should check out the WordPress TextMate Bundle and let us know what you think! This is the first official release announcement and it is bound to have a bug or two, so if you find anything be sure to let us know at the GitHub project page.
Its probably nothing new but I came up with a way to do client side post- or pre-svn actions. Its nothing revolutionary but has already come in handy. The script is *nix only (though I don’t see why the same process wouldn’t work on Windows if it supports command line aliases like *nix does).
I had to write this bash script because we had files at work that needed to be version controlled but still writable by the server process. The need arose because when Subversion updates a file it updates the files permissions with that of the user that did the SVN action. I’m not entirely sure but I think this is because the file isn’t actually updated, but replaced by Subversion (if anyone can confirm that, I’d appreciate it).
After a while of using and not using this plugin I decided that it needed an update. The previous version would simply insert paragraphs of lipsum but now the plugin is set up to return a few helpful elements as well.
We needed a shot of a server room crowded with janitorial equipment. Something that no IT Manager would ever let happen, not even if the equipment were dry and empty and if everybody “promised to be careful”. Just not gonna happen. So I got permission to shoot our server room and then reconstructed the angle in another part of the building to get the equipment at as close an angle as possible. Next I composited them together, added some suds and a puddle and opened up the right side to fit the banner design I wanted to do.
This photo shoot didn’t just yield this composition. I also came out with a fantastic shot of the Server Room at work – a typical “Hero” angle. Because of the tricky lighting and that I only had 2 functional flashes with me this ended up being a composite of multiple shots.
Maybe its a bit cliche, but its fun imagery. We wanted recovery to be right around the corner, or just over that hill. Once a good stock image of a roadway was found I constructed the road sign in PhotoShop to make the scene. Pretty straight forward but a fun use of smart objects and vector drawing tools.
Logo built for a loosely fit freelance group that I do work with. We mostly just bounce ideas off of each other but we did manage to put together an XHTML DashBoard Widget for OS X and partially finished website to go around it. Because of our total disregard for the ‘nut’s integrity he finds himself in some funny places.
Home page: FuzzyCoconut.com.
The name plays off the older Web 2.0 trends of funky names being copied from Flickr and constant beta status of a lot of emerging projects. The XHTMLr is the beginnings of an online companion to the Fuzzy Coconut XHTML Reference Widget. Designed to be clean and straight forward it still needs a database expansion to have more detailed sample information since we have much more room to work than we did in the widget.
A logo for a small group of students who were starting a blog. It was chosen during an informal contest on a web forum. Those funny bobble headed canadians eventually lost interest, but the logo still stands proud.
Home page: Today’s Hot Topics.