(Comments are closed on this entry — any bugs or other issues should be reported on the original fmTuner page. Thanks!)

Of particular note is the customizable Display Format option. Using simple tags like [::artist::] and [::image::] intermixed with regular HTML, you can tweak your Last.fm tracks exactly how you like, or however your WordPress theme requires. You have full control!

Requirements

• WordPress 2.5 or later.
• PHP 5 or later (fmTuner uses PHP 5′s SimpleXML for decoding Last.fm data).
• Basic knowledge of PHP, HTML, and WordPress.

Installation

• Upload “fmtuner.php” to a directory inside “/wp-content/plugins/” directory. For example: “/wp-content/plugins/fmtuner/fmtuner.php”
• Ensure “/wp-content/plugins/fmtuner/” is writable by your webserver (chmod 755 fmtuner).
• Activate the plugin through the “Plugins” menu in WordPress.
• Set up options in the “Settings” menu in WordPress.
• Place “if(function_exists(‘fmtuner’)) { fmtuner(); }” in your templates, between PHP tags.

Release History

• fmTuner 1.1
  Released on Feb. 1, 2010
  Added a placeholder image field to the fmTuner Settings page, which will be substituted when tracks have no artwork.
  Tested under WordPress 2.9.1.
• fmTuner 1.0.8
  Released on Nov. 3, 2009
  Fixed a bug with the [::url::] fmTuner tag that caused Last.fm links to appear incorrectly.
• fmTuner 1.0.7
  Released on Apr. 23, 2009
  Tracks with foreign character sets now display more accurately.
• fmTuner 1.0.6
  Released on Mar. 29, 2009
  You can now display more than 10 Recent Tracks, and you should get fewer tracks without artwork.
• fmTuner 1.0.5
  Released on Mar. 22, 2009
  Track information is now properly escaped to handle $ signs, quotes, and other non-alphanumeric characters.
• fmTuner 1.0.4
  Released on Dec. 14, 2008
  Made minor tweaks for fmTuner Settings page under WordPress 2.7.
• fmTuner 1.0.3
  Released on Nov. 15, 2008
  By request, a [::number::] fmTuner tag has been added, which emits a sequential number for each track (starting at 1). This is particularly useful for CSS and JavaScript display purposes.
• fmTuner 1.0.2
  Released on Oct. 5, 2008
  Added a cURL-based alternative to file_get_contents to hopefully resolve “URL file-access is disabled” issues. If allow_url_fopen is disabled in the php.ini, cURL will be used to fetch the Last.fm feed instead.
• fmTuner 1.0.1
  Released on Sept. 9, 2008
  Added better failure checking and informational messages, removed development code, and updated instructions.
• fmTuner 1.0
  Released on Sept. 6, 2008
  Initial release.

Released under the MIT License. Do with fmTuner whatever you wish. Mod it, mash it, hack it. Make it yours.

The new administration system now sports a minimalist and streamlined look without skimping on the options you’ve already come to know and love. The oft-ignored Dashboard screen has been refined to a now usable level, and the Manage section has seen a nice overhaul as well. For newcomers, the controls are far less intimidating, but all the bells and whistles seasoned bloggers need are still easily within reach.

Keeping WordPress itself up to date is sometimes a hassle, but any plugins you employ also need periodic replacement. With WordPress 2.5, plugins can be upgraded right in place, though WordPress itself continues to only notify you of available updates. Still, the feature is a very nice touch for those who use several plugins like the spam-defending marvel that is Akismet, Google Sitemaps, and so on.

From a reader’s perspective, the new version offers improved speed. One of my biggest gripes about WordPress is how it tends to buckle under a heavy load, and it appears that the new version will be able to dispatch content to visitors’ browsers much faster than before, reducing the workload when under stress from a Digg or Slashdot stampede to a particularly popular post.

Overall, WordPress 2.5 is a highly recommended upgrade for anyone currently operating a blog, and a must-have for those of you still on the fence. What are you waiting for? Get WordPress and get writing!

A small teaser for a project I’ve been working on…

While I was in the process of tidying up, I also fixed the ugly /index.php/post-name/ addressing system I used previously. For the time being, I’ve fixed all past posts with a rather large .htaccess hack, hinting to browsers and search engines that the content has permanently moved to a new address (HTTP code 301). All old links should point to their new locations, and the new system should work as well.

If anyone happens to notice something broken around here, a comment or email would be appreciated so I can get to fixing it!

(On an unrelated note, please forgive the lack of recent updates. Not too long ago, I finally got myself a full time job and have been rather busy with it. I’ll do my best to keep the tech coming!)