Blosxom 2.1.0 released
July 22, 2008.     Axel Beckert

In 2005 Kevin Scaldeferri took over the Blosxom development from Rael Dornfest and opened a SourceForge project for Blosxom. The final 2.0 release and two maintainance releases followed. The user mailing list has been moved from Yahoo! to SourceForge, a developer mailing list has been opened and the IRC channel #blosxom on irc.freenode.net has been established.

Kevin also managed to establish a solid developer base and the Blosxom Development Team grew to currently nine members from all over the world.

Although there were no release in the last two years, the increase in developers led to a nearly permanent development and also to a closer contact with e.g. the maintainers of the blosxom package in Debian.

So the Blosxom CVS repository nowadays does not only contain the CGI script itself, but also plugin-sets and a test suite for easier noticing of regressions. Kudos for the test suite go to Gavin Carr.

While the first few releases after Kevin took over Blosxom were close to Rael's code, the code has evolved a lot over the last two years and it's time for a new release with new features.

And here is it: Blosxom 2.1.0 has been released and features among others the following improvements.

New features

  • Support for external config files and multi-instance installations via environment variables. (Inspired and loosely based on the Debian patches for Blosxom 2.0.2.)
  • Support for multiple plugin directories using $plugin_path and @INC.
  • Support for configuring the plugins to use in a config file.
  • The default feed templates are now in RSS 2.0 format and prevent duplicated stories in feed readers or aggregators if posts are changed after publishing using a GUID element in each feed item.
  • There's now an encoding setting which controls what charset your blog and feeds should be marked as.

Bugfixes

  • Works together with a broader range of CGI.pm versions.
  • The number of false positives when trying to parse dates out of the path have been reduced.
  • Some RSS and XHTML escaping issues have been fixed.
  • The default HTML templates now conform to HTML 4.01.
  • Many small bugfixes and improvements.

Helpers for Developers

  • Test suite
  • Some code refactoring (including a .perltidyrc)
  • Easier building of tar balls for distribution

(Please note: The Blosxom Yahoo! Group as well as the blosxom.com website are deprecated and are no more resp. not supported by the current Blosxom developers.)

Click the button to

 

britta wrote
2008/7/26 12:01:17
Blosxom lives!
If we're using the old version of Blosxom and it works fine, is there an advantage to upgrading to this new one? Would it break anything?
Henk de Haan wrote
2008/7/26 12:48:41
Works fine
In my case the new and improved Blosxom upgraded without any problems, all my plugins kept working ;-)