<?php
 
class SiteController extends Controller
{
    /**
     * @return array action filters
     */
    public function filters()
    {
        return array(
            'accessControl', // perform access control for CRUD operations
        );
    }
 
    /**
     * Specifies the access control rules.
     * This method is used by the 'accessControl' filter.
     * @return array access control rules
     */
    public function accessRules()
    {
        return array(
            array('allow',  // allow all users to perform 'login'
                'actions'=>array('login'),
                'users'=>array('*'),
            ),
            array('allow', // allow authenticated user to perform any action
                'users'=>array('@'),
            ),
            array('deny',  // deny all users
                'users'=>array('*'),
            ),
        );
    }
 
    // The rest of the SiteController implementation
 
}
 
?>

I am not sure if this is the best possible solution, but since it is simple and elegant I am inclined to think it is.

1. The decision has been made to drop the DocBook based documentation in favor of a regular man page. Man pages are still the standard and enough converters are freely available to convert the documentation to any possible format.
2. AScopy now recognizes when a file is new but a copy of a file already present or when a file has been moved. A move of a file will look like a copy of a known file and then the removal of that file, but at least the file can be handled locally on the remote site and does not have to be transported over the network.

The new version can be downloaded here.

For the next version I will probably add the possibility to use different transportation mechanisms like FTP and WebDAV.

So I decided to make a DocBook formatted template for all RUP documents and give the RUP Template Project its own section on this site.

So far only 7 out of the 44(!) templates have been done, but I will try to add one each day (on average). Because of my enthusiasm I decided to release early and often, which means that both the section of the site and the contents of the templates might be a bit ‘rough around the edges’. For now the templates will have to be downloaded individually, but I will provide a gzipped tarball soon.

You can find the RUP Template Project here.

Normally that would cause AScopy to detect the ViM swap-files as new files, but now they can be excluded in the .ascopyrc file like this:

exclude .*.swp

And that is all there is to it. The new version can be downloaded here.

In Bash 3.1 you can do this:

1
2
3
4
5
6
7
8

#!/bin/bash
 
a="1.2.3"
IFS='.'
declare -a arr=( $a )
echo "${#arr[@]}"
 
# Outputs 3 in version 3.1 and 1 in version 3.0

But if you instead do this then it works in both versions:

1
2
3
4
5
6
7
8
9

#!/bin/bash
 
a="1.2.3"
IFS='.'
declare -a arr
eval "arr=( $a )"
echo "${#arr[@]}"
 
# Outputs 3 in version 3.1 and 3.0

So hopefully the Gallery plug-in is better prepared for the real world :). Thanks to Chris Gratham for helping me out with this.

The new version can be downloaded here.

You can download the new version here.

It has been tested on the for the following releases:

• 3.0
• 3.1
• 3.2
• 3.2.3
• 3.3 RC5

The major problem that needed to be fixed is that the plug-in uses standard NanoBlogger calls as often as possible. This means that the standard entry format can be used and even that (from version 3.3) the format field can be used to put markup into the entry.

Unfortunately the NanoBlogger API has changed a bit between versions. The call to read_metadata does not fill the same return variable in the versions mentioned above:

• $NB_Metadata for version 3.0 and 3.1
• $META_DATA for versions 3.2 and 3.2.3
• $METADATA for version 3.3

There was already a function in the plug-in to determine for two given version numbers which was the newer one because the parameters to read_metadata also needed to have $METADATA_CLOSETAG specified from version 3.3 and up if the entry’s body is requested. So the plug-in already had to choose between two different calls based on the NanoBlogger version.

But everything seems to be fixed for now. The new plug-in can be downloaded here.

If you ever want to set up an open source project like this then be prepared to put a lot of time in the initial set up. Stuff like getting SourceForge and FreshMeat working correctly for your project is a lot of work.

I hope they are as useful to you as they are to me. If there are any questions or remarks then please contact me.