Flux CMS DevBlog

All you have todo is adding the following in the config.xml of your collection:

<?xml version="1.0"?>
<bxcms xmlns="http://bitflux.org/config">

    <plugins>
        <parameter name="xslt" type="pipeline" value="tagcloud.xsl"/>
        <plugin type="navitree">
        </plugin>
        <plugin type="tagcloud">
            <parameter name="locations" value="/blog/"/>
            <parameter name="maxfontsize" value="56"/>
            <parameter name="minfontsize" value="20"/>
        </plugin>
    </plugins>
</bxcms>

and a little xsl to display the data:

<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:blog="http://bitflux.org/doctypes/blog" xmlns:bxf="http://bitflux.org/functions" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns="http://www.w3.org/1999/xhtml" xmlns:php="http://php.net/xsl" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rss="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" exclude-result-prefixes="xhtml">
    <xsl:import href="master.xsl"/>
    <xsl:import href="../standard/common.xsl"/>
    
    <xsl:output encoding="utf-8" method="xml" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
    
    <xsl:template name="content">
        <p id="tagcloud">
        <xsl:for-each select="/bx/plugin[@name='tagcloud']/tagcloud/tag">
            <a href="{$webrootW}{path}archive/tag/{name}" style="font-size:{size}px;">
                <xsl:value-of select="name"/>
            </a>&#160;
        </xsl:for-each>
        </p>
    </xsl:template>
    
</xsl:stylesheet> 

have fun :)

... 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

Via Svizzer Blog, I learned that Technorati recommends a rel="bookmark" attribute for the permalinks. So I added that to the blog plugin for hopefully better indexing (maybe not only by Technorati).

Complete explanation.

The latest FCKEditor (used for the blog editor) has some problems with Firefox 1.0.x (and Mozilla 1.7). We couldn't track down the problem until now and the FCKEditor website has not released a new version until now. We try to solve the problem as soon as possible, but in the meantime, we recommend to update to Firefox 1.5, which doesn't have the problem.

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

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

Like written in my other post, I added now akismet support to the Blog plugin (in trunk aka 1.5-dev). It's used as a last resort, when all our own checks don't catch it. So far, it's working great and already caught one of those handcrafted spam comments (all others were labeled as spam before akismet had to do anything)

If you want to use Akismet, you need your own API key from them, and put that into config.xml with the following lines

<blogAkismetKey>yourkey</blogAkismetKey>

and that's it. We will make that option available later also on the site-options page in the admin.

We used the Akismet PHP 5 class by Alex for a really easy integration of the service.

BTW, we still think that captchas are the wrong way to tackle the whole spam problem (they don't help with handcrafted comments or trackbacks anyway) and only discourage legitimate users to comment at all. With all our anti-spam features we have now, we should be on the right track to avoid having to use captchas even longer (hopefully forever). Nevertheless, there is captcha code in the CMS, which can be turned on via an option, it's just not really tested yet (as noone is using it :) )

And here comes a new cool feature for the upcoming 1.5 release. The Blog Sidebar Editor. You can now rearrange, delete, add new "widgets" (term stolen from wordpress) to the 2 sidecolumns of your blog. It's hard to describe, therefore I made a little screencast which should tell more than thousands words:

To make your old blog.xsl working with the sidebar editor, you have to change your blog.xsl a little bit. Search for the following templates and replace them with:

<xsl:template name="contentRight">
  <xsl:apply-templates select="/bx/plugin[@name = 'blog']/xhtml:html/sidebar[@sidebar=2]"/>
</xsl:template>    
<xsl:template name="leftnavi">        
  <xsl:apply-templates select="/bx/plugin[@name = 'blog']/xhtml:html/sidebar[@sidebar=1]"/>
</xsl:template>

And if you didn't include it already, also add on top:

<xsl:import href="../standard/plugins/blog.xsl"/>

That's it. And if it doesn't work for you or you have problems with it, just ask, we're more than happy to help you out.

BTW, it uses the script.aculo.us library for those wondering.

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>

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