Flux CMS DevBlog

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.

... actually, that feature existed since last June, but we never publicly announced it :)

So, here it is:

If you want to make certain blog posts only available to some people you can now do that without giving them access to the admin, even on freeflux.net. For that do the following:

- Create a user in your admin (Top right under "Bookmarks" -> "Users") and give him/her the "Group ID" 2. Users with Group ID 2 can't login into the admin, but they can see your private posts.
- Make a blog post and set the Status to "Private" (can be found under "More options")
- To make the login easy for the users, drag'n'drop the login "portlet" into your sidebar (Can be found in the "Sidebar" Tab in the blog admin), if it's not already there.

Now you see a "Login" link on your blog, if you click on it, a little login opens and your users can login there and then see the private posts, as well

Hope that helps and if you have any questions, just ask them here

Due to some abuses on Freeflux.net, we disabled the possibility to download some file types like zip and exe (like it was with .html for quite some time due to spammers)

Sorry for the inconveniences, but the whole thing got out of hand...

And if you try to circumvent this, we reserve the right to disable your account without any further notice.

We just upgraded the Freeflux.net accounts to Flux CMS 1.5.

For people with customized themes (changed xslt) not everything of the new features will work out of the box. We will fix them manually and continously (especially the comment preview feature needs adjustemens) and also document it here later.

If you have problems with the new version, please report it here or in the forum

What's new besides a lot of bugfixes (in short):

- FCKeditor upgraded to 2.3.1
- new sidebar blog plugin (more)
- blog comment preview
- microsummaries and opensearch support
- akismet support (more)

- event handler für dbforms

- javascript based mail obfuscation (via Popoon)
- built-in fulltext search for Xhtml resources (DB based data are easily integrated)
- new advanced permission plugin
- new assets editor

Annoyed by the forced Google ads on freeflux.net? You don't have to be anymore. You can turn them off now, even on the free accounts.

Just log into your account, click on the "Ads" tab in "Freeflux Info", click the link to turn them off, and gone they are. You can turn them on again later, if you like to support us somehow.

Of course, we don't mind, if you leave them, where they are now and we reserve the right to introduce them back again, if we feel it's needed (for example, if you're producing a lot of traffic). But for the time being, enjoy your ad free Freeflux, if you prefer it that way.

As mentioned in another post, Flux CMS can be made cocomment enabled (or if you install it, it already is). But our comment form has slightly changed with the 1.4 release of Flux CMS, so you maybe have to adjust the cocomment code in your blog.xsl. The correct code is now:

<xsl:if test="$singlePost = 'true'">
<xsl:variable name="entry" select="/bx/plugin[@name = 'blog']/xhtml:html/xhtml:body/xhtml:div"/>
<xsl:if test="$entry/@blog:post_comment_allowed='1'">

/* cocomment elements*/
var blogTool               = "Flux CMS";
var blogURL                = "<xsl:value-of select="$blogroot"/>";
var blogTitle              = "<xsl:value-of select="$dctitle"/>";
var postURL                = "<xsl:value-of select="$blogroot"/>archive/<xsl:value-of select="$entry/@blog:post_uri"/>.html";
var postTitle  = "<xsl:value-of select="$entry/xhtml:h2/text()"/>";
var commentAuthorFieldName = "name";
var commentAuthorLoggedIn  = false;

var commentFormID          = "bx_foo";
var commentTextFieldName   = "comments";
var commentButtonName      = "bx[plugins][blog][_all]";

</xsl:if>
</xsl:if>

Hope that helps

but we're online again as soon as possible, looks like some internal network issues and nothing major...

Update: And now it's working again... Some internal routing issues prevented that the packages went to the freeflux server :( Now also has a new IP (from the new data center), so the pending move one floor up won't be of any major hassle now :)

After popular demand, we changed the mod_rewrite rules, so that you can have now your own favicons for your Freeflux installation.

Just upload the file named "favicon.ico" to your files-folder and it should work (maybe a browser restart or cache-flush is needed before you'll see it)

Flux CMS is now cocomment enabled. It comes with the default themes, but you can add it to your theme by yourself. Just add the following code to blog.xsl somewhere in a <script> block.

<xsl:if test="$singlePost = 'true'">
<xsl:variable name="entry" select="/bx/plugin[@name = 'blog']/xhtml:html/xhtml:body/xhtml:div"/>
<xsl:if test="$entry/@blog:post_comment_allowed='1'">
/* cocomment elements*/
var blogTool               = "Flux CMS";
var blogURL                = "<xsl:value-of select="$blogroot"/>";
var blogTitle              = "<xsl:value-of select="$dctitle"/>";
var postURL                = "<xsl:value-of select="$blogroot"/>archive/<xsl:value-of select="$entry/@blog:post_uri"/>.html";
var postTitle  = "<xsl:value-of select="$entry/xhtml:h2/text()"/>";
var commentAuthorFieldName = "bx_fw[name]";
var commentAuthorLoggedIn  = false;
var commentFormID          = "bx_foo";
var commentTextFieldName   = "bx_fw[comments]";
var commentButtonName      = "send";
</xsl:if>
</xsl:if>

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 :) )