BLOSXOM

Nuno from Nunonunes.org has developed a new plugin to include the Disqus feedback system into a Blosxom-Blog.

It is perfectly possible to add the extern feedback functionality just by tweaking the flavour templates, of course, but this plugin makes it easier to use and also makes it possible to port existing sites to Blosxom and easily maintain the comments that may already exist. It also allows for the individual turning on or off of feedback on a per-story basis: Download & Infos

This site is a mirror of the great Blosxom-project from Douglas Nerad, who has built up "The Unofficial Blosxom User Group".

Most of the updates and the development of the "Unofficial User Group" is outdated and you'll also find recent versions of Blosxom and plugins at the active developer-community at SourceForge today.

The old collection was & is still a great archiv, so I contacted Douglas Nerad at the begin of April and asked him, if it's ok, that I mirror his plugin-collection, before he closes the site in the near future - and he said 'yes'. So thanks a lot - he worked hard on the project for a long time - so all kudos to him!

You'll find here very soon the plugins & flavours for Blosxom and also some Updates & News from the development of the recent Blosxom-Project. I'll also work on the layout in the next weeks and some improvements, so there will be a lot of changes and updates - please keep that in mind - but first of all, i'm working on the transfer of the huge plugin-collection - so just give me some time!

Blosxom 2.1.1, the "never trust a dot zero release" bugfix release for 2.1.0, has been released - it mainly fixes two bugs.

Lilo von Hanffstengel noticed that the GUID in Blosxom 2.1.0 was not working as link and therefore isPermalink shouldn't be set to true. This has been set back to "false" for the default RSS story template. This won't change the GUID itself, but prevent it from being used as link anymore. That's what the tag is for anyway.

$url, which contains the base URL according to the documentation, contained the complete URL in some cases, e.g. when called from inside an SSI document. This has been fixed in 2.0.2, but caused the problem to show up in other situations. The (at least with Apache 2.2's environment) no more working manual base URL detection code has been rewritten. It has been made simpler and easier to understand. And it only applies if the base URL was not set manually.

In those rare cases where neither CGI.pm nor Blosxom manages to correctly determine the base URL, you can easily set $url in the config file to the correct value and no base URL magic happens anymore (except the removing of a trailing slash if present — as before). This closes issue #2032685. This news is archived from the old Unoffical Blosxom User Group!