A store for the bits of code I'm always forgetting...
Get social with Gary: TW | FB | G+ | LI | [Read More …]
To get developer API (application programming interface) access to several of the Google services, you need to have an API key. This is so Google can tell who is accessing the service, and ensure that each person stays below the courtesy daily limit for the number of requests.
Here we look at how to allow access for, and get a key for, the Google Web Fonts API.
Jenkins, powered by my Phing build file
On my computer I have Jenkins installed for viewing analysis of code, and as I code with PHP and not Java, I use Phing instead of Ant as the build system. I run several PHP programs against the code I’ve written or auditing, and automate the creation of API documentation using DocBlox, as well as send that documentation via FTP to a docs subdomain.
I’ve refined my build file over time, but it has always been pretty much an identical file duplicated over many projects, and this wasn’t scaling well as I found the need to refine it further. Instead, I discovered the ImportTask in Phing, which meant I could have one generic build file kept outside of my project folders, and import that into each bare bones project build file and amend as necessary.
This post is an update to a previous post on the Genesis Grid Loop.
That previous post had some shortcomings, especially concerning the number of grid posts and the number of posts as set in Settings -> Reading. If they didn’t match, then WordPress would declare one or more pages at the end of the pagination for those query of posts as being a 404 Not Found. We needed a better solution, and between legendary Genesis developer Bill Erickson and myself, we’ve come up with one.
Visually split the primary sidebar in Genesis into two further sidebars, each with their own widget area. For more info about genesis_register_sidebar() see the StudioPress tutorial on How to Register a Widget Area.
When uploading large images over an approximate size (~2500×2000) I was encountering the HTTP Error message when trying to crunch the image (which ultimately fails and doesn’t produce the smaller pre-defined image sizes).
After trying several solutions, the following appears to have solved it for my setup, once and for all – add this to your .htaccess file: