Just added a new cool (IMHO) feature to BxCMS. Creative Commons support. From now on you can go to Site-Options and insert the link to your chosen license in the "cclink" field, eg "http://creativecommons.org/licenses/by/2.5/". Everything else is automatically extracted, the button will show up on your blog and the correct RDF snippet is inserted. And the link is also added to the RSS feed. Furthermore there's a copyright field in Site-Options for adding your copyright notice, which also will be added to the RSS.
For more information about Creative Commons see their webpage, you can create your own license with a few mouse-clicks here,
Freeflux.net is also updated, but the "button in blog" will only work for those, which not have changed their blog.xsl. All other have to add it manually. The diff can be found on our svnweb.
People using BxCMS and not on Freeflux also have to update their db. Just go to http://yourdomain.org/webinc/admin/update/ and it should happen automatically (after you logged in, of course)
I added the possibility to use the fileinfo extenstion to inc/popoon/helpers/mimetype.php instead of the command line "file" utility. Should be more performant (and one less command line thingie we need...). If the extension is not found, we still go to the "file" program.
New Blog Comment mail notifications now contain a direct link to the db-entry for approving/deleting/editing.
We had to change some code in the login procedure, so you have to update the whole tree as the affected files are spread all over the place ;)
You also have to update xml/blogcomment.xml (which is not in the bxcmsng tree but in the bxcmsdemo one), just take the one from the original (or if you still have svn linked to it, an svn up will be enough there). And here's the diff, if you want to change it by hand.
As a suggestion by Sven, we also strip the "br"-tags from the mail to make it look less ugly...
We try hard not to change the db structure. At least in stable branches. And if we do, then it's usually in a backwards compatible manner.
Since quite some time we have the dbupdater tool, which can be invoked with
http://yourdomain.com/admin/webinc/update/
(after you logged in as admin). This tool automatically checks, which updates you already have done and which are necessary. It's safe to call that after each update (svn up and similar). If nothing has to be done, it does nothing ;)
Since today, we also have an autoupdate option, which automatically checks, if it needs a dbupdate or not. It is disabled by default, add
<autodbupdate>true</autodbupdate>
to your conf/config.xml in the <options> section.
If that is on, it checks if it needs an update, if yes, it starts the updater automatically. This comes with an additional db-query on each request... We needed that for Freeflux as we didn't want to upgrade hundreds of accounts manually.
If you should set autodbupdate to true or false is your decision ;) If you remember to call/admin/webinc/update/ after updating BxCMS it's save to leave it on false (or at least call it, when you get unexplainable errors ;) )
I adjusted the copyright years in all PHP files (so it also includes 2005). Be not surprised, if the next svn up updates a looot of files ;)
