Now Reading news
I have providing some light maintenance development for Rob’s Now Reading plugin; since Wordpress 2.7 wholly changed its interface, the plugin need some tweaking to make it work.
Up to this point, I’ve been hosting it locally, mostly picking at it whenever time allows.
I just updated it the other day to add a new feature (editable ASIN) and hopefully fix a recurring bug (CDATA error when searching).
In any case, I hope to make a push in the near future to clean it up and submit it the official Wordpress plugin site so that its user can benefit from auto-update, etc. etc. My own much-atrophied skills as a PHP developer aside (I deal mostly with Java at work), I think that it will ultimately benefit everybody, assuming I can make it so that the updates don’t override custom templates (perhaps giving preference to Now Reading template files in the theme folder?).
Stay tuned. The plugin is now here.
Comments on this post are closed. For support, please use the forum feature of the official plugin repository.
Now Reading for Wordpress 2.7
This page has been moved to a more permanent spot. Please go there.
Wordpress 2.5

After 6+ months of steady development, Wordpress 2.5 has finally been released, with a number of new features, including a media library and the first administration panel redesign since 2.0.
In addition, the main Wordpress website has been redesigned to match.
Congratulations to all the hackers, testers, and volunteers who helped it happen.
Semantic Classes plugin for Wordpress
This plugin’s functionality is now largely integrated into Wordpress Core. It is neither maintained nor supported.
My Post Classes plugin from yesterday has morphed into the much fuller Semantic Classes plugin. For a full description/documentation, see its project page.
In brief, the plugin is a combination of modified code from Scott Wallick’s Sandbox and some coding of my own. It seeks to bring Sandbox’s wonderful semantic class generation into plugin form, where it can be easily included in other themes by means of a template tag.
As of v0.2, it provides the following functions:
- Posts
- Return a post’s categories with a modifiable prefix
- Return a post’s tags with a modifiable prefix
- Return a post’s author with a modifiable prefix
- Return a post’s date elements (year, month, day, hour) with modifiable prefixes
- Body
- Return a body’s type(s); e.g. ’single’ or ‘archive’ or ‘home’
- Return a body’s date elements with modifiable prefixes; associated dates for entries with date data (see documentation) and current date for searches, home, etc.
- Comments
- Return a comment’s metadata; e.g. differentiate site users, post author
- Return a comment’s date elements with modifiable prefixes
- Return an ‘alt’ class for alternating comments
If you’re interested, give it a whirl. I’m no experienced plugin writer, but I’m pretty pleased with this.
Wordpress Post Classes plugin v0.1
This plugin has been superseded by the much-improved Semantic Classes plugin
I’ve written a small Wordpress plugin that provides some new template tags that return a post’s tags, categories, author, and date; useful for CSS trickery.
You can view its page here.
This initial release provides the following items:
<?php generate_tag_class(); ?>- This function returns a space-delineated list of the post’s tags, prefixed with ‘tag-’
- e.g. tag-politics tag-election-2008
<?php generate_category_class(); ?>- This function returns a space-delinated list of the post’s categories, prefixed with ‘category-’
- e.g. category-personal category-random-thoughts
<?php generate_author_class(); ?>- This function returns the author name of a post, prefixed with ‘author-’
- e.g. author-Heliologue
<?php generate_date_class(); ?>- This function returns a space-delineated list of the post’s date, prefixed with ‘y’ (year), ‘m’ (month), and ‘d’ (day).
- e.g. y2008 m03 d11
Moving blogs and .htaccess
When I first set my blog up, years ago, I installed it to a subdirectory called “/blog” with the vague intention that the canonical “http://heliologue.com” URI could be a landing page pointing to whatever else I wanted to put on my server. Eventually, I learned that I could get to just about anything I wanted using the blog, and used a PHP redirect to point the root URI to “/blog,” which worked well enough.
Eventually, though, I got tired of such a thing, and wanted the blog to reside on the root of my public HTML directory. At this point, though I had a large (sort of) number of incoming links and indexed pages. How would I move without breaking all those links.
Yesterday, I finally bit the bullet and moved my blog up a directory, but the mod_rewrite trick I had in place to prevent 404s didn’t work. Oh noes!
Finally, I stumbled upon this ridiculously simple solution for my .htaccess file:
RewriteEngine on RewriteBase / Redirect 301 /blog http://heliologue.com
And everything works. When someone goes to http://heliologue.com/blog/path/to/entry, the directive will automagically take them to http://heliologue.com/path/to/entry.
Might I add that once I changed the siteurl values in my database, I immediately rebuilt my site’s XML sitemap, which was easy with this little plugin, which will generate sitemaps for compatible search engines (Google, most importantly) and ping them with the change.
Subscribe