GigPress

It’s been a quiet six months on the GigPress front.  Since 2.1, I’ve basically been squashing bugs and adding small tweaks, almost exclusively based on feedback and support requests (I listen, I do!). But client work and life in general has precluded much serious development time, and will likely continue to do so into the summer as well. (keep reading)

I just committed GigPress 2.1 to the WordPress plugins repository; it should start to show up in your plugin update notifications shortly.  Most of what’s new in version 2.1 was covered in my last post, but I wanted to highlight a few changes to prevent headaches: (keep reading)

GigPress 2.0 has by all accounts been very popular with all you folks, and I’m glad to see if being so widely-used and well-received. I haven’t done much work on it since October, but I found some time over the last week or so to incorporate some oft-requested features. (keep reading)

I’m happy today to announce that GigPress 2.0 (formerly known as GigPress 1.5) is available for download. This is a major upgrade that has seen most of the plugin rewritten and a tonne of new features added, and I’m pretty excited to finally have it out the door. (keep reading)

I’ve been on a bit of a development sprint this past week, spending an inordinate number of hours working on GigPress, and the results so far are heartening. I’ve completed a tonne of code optimization and security enhancements, reduced almost all redundancies, and done all of the re-architecting required for the upcoming version. The admin-side of GigPress 1.5 is 90% done, and I’m very happy with it. I figured I’d give a small preview of what’s in store. (keep reading)

I’ve pushed out a couple of minor updates in the past few weeks – just small bug fixes and the like. As always, you can refer to the version history for the dirt. (keep reading)

See that on my face?  It’s egg.  Which is especially gross, as I’m vegan.  But that’s what happens when a one-letter typo in your plugin adds about 30 extra database queries to run on every single page load — in both the front-end and back-end — of a WordPress install. (keep reading)

There’s been much discussion after the release of version 1.4 regarding the fact that this release seems to be bringing some sites to a slow crawl under certain server configurations. There doesn’t seem to be any rhyme or reason to this, as some of these servers are very similar to my own testing server, where GigPress is performing like a champ. (keep reading)

I know, I know, it’s been too long since an update – apologies. However, I think there’s enough in this new version to keep you all happy. (keep reading)

Non-English users of GigPress running WordPress 2.6 will definitely want to upgrade to version 1.3.4, as there was a bug under WP 2.6 that prevented the language files from loading. This release also fixes some XHTML validation issues in the output that somehow went completely unnoticed all this time. (Thanks Martin!)