Accessible websites with Flux CMS

Our partner mediagonal got the AA+ label of the swiss “Access for all” initiative for “Die Volkswirtschaft“, a magazine published by the SECO (State Secretariat for Economic Affairs). This online version of the magazine was done with our Open Source Flux CMS and is the second project for SECO done with our CMS (the other was chance06).

AA+ is the highest ranking you can get from “label4all” and includes all the priority 1 and 2 W3C recommendations plus the additional ones defined by the federal government.

More (german) info can be found in the mediagonal news entry.

Tags: , ,

ArtCast powered by Flux CMS

The Swiss Blog Awards Nominee ArtCast is now powered by Flux CMS. Congratulations to the move.

If you want to switch from twoday to Flux CMS, Hannes wrote a little script which imports your twoday blogposts to Flux CMS.

And regarding the Swiss Blog Awards: If you’re blogging from the awards, tag your posts with sbawlive and they will magically appear on More info at the blog.

Tags: ,

etoy blog now using Flux CMS

etoy is now using Flux CMS also for their external blog. Or better said, they merged the internal and external blog and are using now one tool and one admin to contribute to those sites. Thanks to the integrated permission management, they can decide on each post, if it can be seen by all, or just logged in agents. Soon, the whole etoy website including their next project, mission eternity, will also be using Flux CMS.

More info on their blog by agent.SILVAN.


Flux CMS goes mobile

After my trials with an adapted CSS for handheld devices, Beni started designing a special handheld-only theme for Flux CMS. As you still had to download approx. 50kb of data with the CSS-only approach, we decided to only show the title, date, a comment counter (if there are any) and some navigational items to the overview pages in mobile mode. This brought the initial size down to approx. 4kb. We also changed other XSLT stylesheets for a better experience on mobile devices. So, head over to to see the full glory (If you want to leave the mobile mode, click on the link on the bottom called “Leave Mobile Mode”. The reason for this will be explained in the next paragraph). There are still some rough edges here and there and we could do some more CSS magic to make it look nicer, but it already fulfills its job perfectly as it is right now.

To make the mobile experience more enjoyable, we also added some “handy” features. If you go to a “normal” page of this blog with a mobile phone or a PDA (or opera in Small Screen Rendering Mode), you should see a link on top called “Mobile Mode”, which brings you to, meaning you don’t have to remember the mobile URL at all. The first hit still downloads the full page, but here comes the next feature into play, the remembering-that-you-are-a-handheld feature. Modern mobile browser do handle cookies correctly (at least, the K750i, the P800 and my Palm do, Silvan’s Nokia and Beni’s something-japanese phone didn’t) and therefore we set a cookie, if you go to the mobile mode. Next time you visit us with that device, we can deliver the correct page right away (and this is also the reason, why you explicitly have to click “Leave Mobile Mode”, if you want to see the “real” page again).

You may ask, why not just doing user agent sniffing or let people just bookmark the mobile URL.

User agent sniffing is way to expensive (and sometimes also unreliable) just for the little amount of mobile traffic we expect. There’s a great collection of handheld user agent strings and their capabilities called WURFL, but the XML file is already huge and you’d have to look for each and every request, if it’s a handheld browser and then show the correct page. WURFL is not useless nevertheless, as it also can tell you, what that model is able to render and what not. But we don’t use this right now and just deliver the same page to everyone. Furthermore there are PHP scripts available, which make accessing that large XML document quite easy and relatively fast .

The “why-not-just-bookmark” argument has its flaw, if you’re following a link from eg. a mobile feed reader or another webpage, which usually point to the “normal” version of the page. But if you already have the cookie set for that webpage, you’ll directly see the mobile version, without having to type in the “mobile” URL or accidentally downloading the full page.

Enjoy reading Bitflux Blog on the go. And of course, Freeflux accounts will get that feature during the next update as well.

Tags: ,

Make your Flux Blog handheld-ready in 10 seconds

My K750i (I’m still playing..) didn’t want to display this blog properly. Too much stuff to display. Therefore I made a quick handheld optimized css and now it is at least readable:

The CSS looks like this:

and I added the following to master.xsl:

This doesn’t of course save any bandwidth, but we’re working on that :)

Tags: ,

Geolocation annotated blog posts with Flux CMS

Benjamin and I we’re working on Geolocation support for Flux CMS resp. its blog plugin last week.

You can now either use Plazes for automatically geoannotate your blog posts (like this one) or you can use the tagging system for places where Plazes is not suitable, like if you are on a mobile network. As you can now also tag your posts via mail/mms, you can copy&paste your longitude/latitude data from a gps device into your posts and then the blogpost is automatically annotated. Also in the RSS feed, of course.

More about the Plazes support can be read in this devblog post, and more about the moblogging part in that devblog post.

Tags: , ,

Flux CMS 1.2.2 Security Bugfix Release (codename: “not our fault again”)

Repeat from the 1.2.1 release announcement :)

Yeah, yeah, the PEAR XML_RPC had a big bad security bug (some details) and Flux CMS was also affected (like many other PHP applications) as we include that library.

Therefore we just released Flux CMS 1.2.2 with the new library from PEAR (and some other little fixes, see the NEWS file). Get it on our download page. We’ve additionally also made a small patch available. Just untar it in your BxCMS root folder, it will just replace the affected XML-RPC files, but not the other fixes.

If you’re running a version, which was checked out with svn, you can also do

and you should be fine (of course you can also “svn up” the whole installation). And if that’s still too much work for you, just delete inc/bx/plugins/xmlrpc/weblog.php and you should be fine (but the XML-RPC weblog interface isn’t working anymore then)

We highly recommend that you upgrade as soon as possible.


Freeflux Vandalism :)


Found via Frank’s Blog and you can do that by yourself :)

And by the way, Frank did its own Freeflux Theme called Flix, he said he will release it under the GPL when it’s ready, so stay tuned.

And last but not least, Freeflux and Flux CMS got some attention in the Swiss Blogosphere; Medienpraxis and Stefan Bucher talked about it and krs is switching to Freeflux (

Update: Stefan is now officially using Freeflux for his english blog. Welcome.

Tags: ,

Freeflux Betatester for new admin wanted

Blog posts relaying is lame, I know, but nevertheless:

We plan soon to upgrade all accounts to the 1.3 branch and with that to the new admin look&feel. Therefore we are looking for Beta testers. More info on the Dev Blog.

Of course, this is actually not only Freeflux related, but for the whole CMS, so other users are invited, as well.