In reverse order: the new comment permission scheme will allow blog admins to better specify who can post comments to their blog. The currently available options are anonymous guests, guests with names, registered members of the site, members of the blog and nobody. These options also apply to the viewing permissions of the comments; you can restrict comment creation only to registered users but viewable by all and vice versa: comments created by everybody but viewable only by the blog members. Unfortunately, if you have modified your PostDetails fragment, you will need to replace the comment logic with something like this (watch the line breaks!):

## show the comment counter
#if($properties.detailEnableCommentCount)
#if($commentHelper.isCommentsShown($blog,$post) && $post.comments.size()>0)
[<a href="$link.setPost($post)#Comments">$post.comments.size() comments</a>]
#elseif($commentHelper.isCommentable($blog,$post))
[<a href="$link.setPost($post)#Comments">add comment</a>]
#end
#end

The blog and user management pages are only available to the site administrator and concern themselves only with addition and removal of blogs and users, not setting properties and settings.

The RSS subsystem has obtained a new configuration page where the blog admin can set the default format of the RSS feeds (RSS 2, RDF and ATOM are currently supported), and whether the default should include full posts or only excerpts. Several settings are now admin-settable, such as copyright statements, the address of the editor and the RSS feed language.

Whew, that was quite a bit more than I suspected...

So far the results are very impressive, as there is a noticeable speedup even on the same 100MBit Ethernet segment. Pages are compressed about 70%, taking an extra 7ms on my development machine (unoptimized, debug setup). I think it's worth it.

I've also updated the file upload handling, removing a dependency while at it. Should not affect users at all.

First of all, if you log in and try to administer your blog you will notice that the administation buttons are gone. In layouts/Layout.vm, change the line invoking the DefaultStripe fragment to #DefaultStripe($stripe.cssName $stripe.listName).

Second, in the top navigation, change the <span class="nav user"> tag to contain only the following code:

#foreach($linkTo in $navigationList.getNav("UserActions"))
#if($velocityCount > 1) | #end
#navbutton($linkTo.getLink($data,$link) $linkTo.label) 
#end

This will allow plugins to change the user action links, without needing to change the template itself.

Third, there is a new template tool handling security with the name $securityTool. You can replace all calls to ACLs and all permission checks with this tool. Supported operations include:

$securityTool.canEditThisPost
$securityTool.isBlogAdmin
$securityTool.isBlogEditor
$securityTool.isBlogAuthor

Improvements to the system include:

• Blog URLs have been shortened by removing the prefix /blog/. A redirect is in place that leads to the new addresses.
• A new Root Blog has been introduced that contains the aggregate of all other blogs. This also allows for the themeing of the aggregate blog. URLs without a blog are redirected to the root blog.
• By default, links produced by the system are relative to the site, not absolute. This should lead to somewhat shorter load times on link-heavy pages, and actually implement permalinks, and allowing cookie-less operation.
• The AdminBlog and AdminSite sideboxes should by default show only those actions that the current user can perform.
• Improved compatibility with Internet Explorer due to buttons that would not respond.
• RSS feeds with Unicode characters are working again
• It is possible to view a summary of a whole year by visiting the year link on the location bar. A monthly view is on the works.

After investigating a user report on the unability to map the blogs media folder, I have found these interesting facts:

1. Web Folders needs the whole path, from the server root up (/), to be WebDAV-enabled, even if I just want to map a specific path. This breaks, as blogentis maps the WebDAV folders deeper into the tree, and the path segments leading to these folders produce redirects to HTML pages.
2. For some reason, while it requests authorization, the HTTP headers of the response have an empty password set.

Standards are good, you have so many to choose from (and apparently get them wrong)...

I've removed all names of the former blog name, done all the package-moving work, and registered the project on SourceForge. I'm currently investigating maven-ification of the project, and the results seem encouraging so far. Source code is not yet available on the project pages, but the final license will be the GNU Lesser General Public License.

I've updated the site, the improvements/bug fixes are:

• Unicode characters work again in templates.
• Saving templates/files as Zip files works.
• Comments have been added to (almost) all templates indicating their role, extra parameters they provide etc.
• Unicode characters should work correctly from non-web-folders clients in Slide.

I've also added support for LDAP-based user account information, but it is not enabled because I'm not satisfied by the current security status of blogentis - SSL is a must, and appropriate redirects have to be implemented.

Meanwhile, I'll be cooking up some more plugins...