We're very proud to announce René Moser as new committer with SVN access to Flux CMS. He already committed a nice visual user-feedback feature, when uploading new files. Now users with slow connections see, that they have to wait while uploading the file.
Many thanks to René and welcome to the Flux CMS developer community. Let there be a lot of contributions :)
I finally made the sites, which should be pinged after each new blog entry, configurable. You can do that now in the Site-Options (defaults are technorati and pingomatic.com plus planet.freeflux.net, but that doesn't do much right now :) )
Beni wrote an integrated themes installer for Flux CMS. You can now install themes directly from the admin interface without the "download zip/upload zip" cycle needed before.
You'll find the theme installer on the start page of the admin in the "General Options" Box under "Download more themes".
The available themes are described in a simple XML file centrally located on our server. If you'd like to include your theme in that XML file, just send us a mail with the necessary info.
We just added anchors for individual comments in the blog plugin. You can now directly reference a single comment with for example http://devblog.flux-cms.org/archive/2005/11/30/blog-editor-problems.html#comment187. This format is also used in the notification emails.
Another item implemented from the WishList :)
Since writing an own "Flux CMS"-Plugin can be quite a challenge, there is now a very basic "HelloWorld"-Plugin documented in the Flux CMS-Wiki.
Since the update to FCKeditor 2.1.1, some people reported issues with saving posts. We finally could reproduce and found the problem. FCKeditor added s to the code, which made our XML parser on the server choke and lead to the now well-known errors. This is fixed now, as we now dereference undefined html entities on the server side and first tests look very good :)
As FCKeditor is quite heavy and not all need a WYSIWYG editor, we now added the possibility to always use the plain-text Source Editor. Just go to the options and switch BlogDefaultEditor to the Source Editor and the blog editor then will always use it. We also added some buttons to the Source Editor, so that you don't have to remember all those html tags. Thanks to Alex King for his quicktags library, which made the integration pretty easy.
By the way, if you set (or leave) BlogDefaultEditor to 'wysiwyg' and use the blog editor with a non-wysiwyg capable browser (like safari, konqueror or opera), Flux CMS will automatically switch to the Source Editor then (as it did before).