We updated FCKeditor to version 2.6.3 on trunk and the 1_5 branch. It is also already deployed to freeflux.net.
Besides solving issues with Firefox 3 (and many many other bugfixes since our last update), this adds support for Safari 3 and Opera 9.5 for this WYSIWYG Editor.
If you encounter any problems with this update, please report them in our bugtracker.
Even though Flux CMS was always UTF-8 capable, we stored the content entity encoded in the database as MySQL 4.0 was not unicode ready. That changed with MySQL 4.1 and Flux CMS is now finally capable of using it (in the trunk version). If you install it from scratch and let the installer create the database, it will now automatically use the UTF-8 mode (if you have MySQL 4.1, which is highly recommended). If the DB already exists before you install Flux CMS, you should change the default character set to utf8 (see below) before the installation.
If you want to switch an already existing installation to UTF-8 mode, you have to do the following (if you don't do anything, it will still use the "entity-mode", so you don't have to "upgrade". Meaning, if your default character set and colaltion is not utf-8, the old mode is used)
Call
http://yourdomain.org/admin/webinc/update/
export the database with
mysqldump --skip-opt --extended-insert=false --compatible=mysql40 -Q --add-drop-table --complete-insert fluxcms > fluxcms.sql
(or similar that's just our default). Then do
ALTER DATABASE `fluxcms` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci
and import the dump again with
mysql fluxcms < fluxcms.sql
without any warranty :) The old entries still will be entity encoded, but new ones not anymore.
Get it, while it's hot :)
There are way too many changes since the 1.2 release. New admin design, more blog features and many others, we lost track, as well...
See also this post for some info about switching the branch.
We plan to release more often in the future, with the new subversion layout it should be easier. The immediate plans for the 1.4 release aren't that big and could be not that far off.
The 1_3 branch will now only get bugfixes, new features go only in trunk. It's at the moment quite safe to use trunk, as we use this for projects we're currently working in. That's also the reason, why there almost certainly will be a 1.4 release soon.
Writing a new plugin in Flux CMS is an easy task, if you know how :) But now, it's even easier. I wrote a little script, which takes all the necessary tasks off you. Just call from the commandline:
php inc/bx/tools/generate/plugin.php
give the plugin a name and the script will generate the following files:
inc/plugins/yourplugin.php
themes/{folder}/yourplugin.xsl
data/yourplugin/.configxml
And you can start coding (and directly testing it with calling http://example.org/yourplugin/)
But it can more than that. If you already have a database table with data, which the plugin should use, you can tell the installer that (without the table prefix). It will then automatically create the necessary dbforms2 XML document (in the dbforms2/ directory), so that you can directly start editing the data with dbforms2 (just call it with http://example.org/admin/dbforms2/tablename/). The example XSLT and the plugin also uses then this DB data, outputs it as overview and in detail view.
Notice: The table needs to have the correct tablePrefix (bxcms_ by default) and a columns named "id".
Hope that helps in creating new plugins and getting started faster with Flux CMS.
Update: I made a little screencast about setting the db-table up, creating the plugin and editing the data with dbforms2 (there's no audio, btw :) )
The amount of trackback spam we get is amazing. It's all (or most of) rejected due to our spam filters, but it's still unnecessary (Most of you won't detect it anyway, as we don't send rejected comment notification mails by default). To at least cut down that a little bit, we added a new global option (goes into conf/config.xml): "blogTrackbacksTimeLimit". If that is set to true (it is by default), trackbacks are disabled after one month. I think, that in very few cases one has to trackback a post, which is more than a month old (very few people trackback at all anyway). And if you leave the comments open, that person can still do a "Manual Trackback" then.
I put this into the 1.3 branch as well, as it shouldn't break anything (but as usual, you should delete the tmp/dir after an update).
If you have a customized theme, you have to adjust blog.xsl, so that it doesn't display the trackback url anymore, if trackbacks aren't allowed. See the diff for what has to be done. If you don't change it, trackbacks are still not accepted, just the text on the post itself is missleading :)
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 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).