We plan soon to upgrade all Freeflux.net accounts to the 1.3 branch and with that to the new admin look&feel. Before it hits the masses, it should be tested a little bit more. Whoever likes to do that, drops us a note, either here in the comments or via the contact form.
You can either open a new Freeflux account specifically for this tests or we just upgrade your existing account already now to the 1.3 branch. The upgrade should be painless and if something nevertheless goes wrong, we do have backups :)
If you start testing and hit some bugs or have other suggestions for improvements, just post them to the forum.
Some other features relevant for the common Freeflux user we added to the 1.3 branch are:
- Blog: Improved spam checker (check against XBL, works with "default" DNS servers) (more)
- Blog: Tags for entries (more)
- Blog: Added geolocation properties (more)
- Blog: Added bookmarklet code (JustBlogIt compatible) (more)
- Editors: liveSave for oneform editor added (more)
- Editors: Updated Kupu-Code to latest release (more)
- dbforms2: Replacement for very old dbforms code (more)
BTW, the dbforms2 layout will change a little until the official update.
Thanks for your help.
We committed the new admin code today in the trunk. Not everything is done, the actual "edit" pages just turned blue. But the login and the overview pages sport now the new design. There are still some little quirks here and there which we will sort out in the next days (additionally to the further refinements).
If you don't have a local copy of the trunk, you can check it out at http://trunkdemo.bitflux.org/ (demo/demo).
Freeflux.net will be updated, as soon as we think the new layout ready :)
The design was done by monorom.com, many thanks to her.
As requested by Mario (but it was actually on the TODO list before), I implemented a "LiveSave" feature for the oneform editor or in other words Save-Without-Reloading.
If you edited documents (like xsl or css files) in the oneform editor, every-time you clicked (or hit alt/ctrl-s) submit, the page was reloaded, the cursor position lost and it showed you again the top of the file. Pretty annoying, especially with long documents. Not anymore :) We use now XMLHTTPRequest in the background for doing the save, which prevents the needed reload. Works on Win/IE, Mozilla/Firefox and Safari.
It's not bulletproof right now, if the save didn't work, you won't be notified, it still says most of the time "Document saved." :) Will try to fix that later. (But if the file is not writable, which is the most common "error", it will warn you on opening the editor.)
Update: The oneform editor now also checks for well-formedness of XML and HTML documents. This will prevent saving non-valid documents and producing errors. Tested on Firefox, does not work on Safari (but liveSave in principle still works, just not the well-formed-check), not tested on IE (but IIRC should work there as well).
I just committed a bunch of patches to support a MySQL Replication setup.
If you're using MySQL Replication with a master and one or more slaves, you should only write to the master (but you can read from all the slaves). We adjusted now the CMS, that all DB writes go to a different object than the reads. If you don't use replication (and just leave the config as it is), these won't be actually two objects, it's still just one MDB2 object. The popoon_pool class takes care of that.
For developers, this means that they should now use for all there DB write operations $GLOBALS['POOL']->dbwrite and for the read operations $GLOBALS['POOL']->db, as it was before. If you have to read from the DB immediatly after you wrote from and (and you're dependent on the written data), you should also us $GLOBALS['POOL']->dbwrite for reading in that case (cause of possible lag), but really only then. Otherwise you loose all the advantages of MySQL replication :)
People who just want to use that feature in their setup, see the example config file, should be quite self explanatory.
BTW, it's not that Flux CMS is extremely slow that we need that, but we're currently working on a project, which expects a lot of traffic in a short period of time and we want to be better safe than sorry :)
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)
