# apt-get install cups splix

Then go to the CUPS admin site at http://localhost:631/ and then Administration, Add new Printer, click through and select the splix driver for the ML-1610. That’s all.

I think the first time I tried I just hadn’t installed the splix driver… which is easy enough to find:

$ apt-cache search samsung driver

One of the problems is that the WordPress Ajax handler script is located in the admin directory. So password-protecting the admin area will break all Ajax functionality your blog might be using.

First, see this tutorial on how to password protect directories with an .htaccess file. Sivel has an example for whitelisting the Ajax handler, add these line to your .htaccess file:

# These are the lines that do the password protection.
# You probably already created them while reading through the tutorial linked above.
AuthUserFile /path/to/your/htpasswd
AuthType basic
AuthName "Restricted Resource"
require valid-user
 
# This is the whitelisting of the ajax handler
<Files admin-ajax.php>
    Order allow,deny
    Allow from all
    Satisfy any 
</Files>

Please notice that you absolutely need to create the htpasswd file, see the linked tutorial above.

Here’s the necessary configuration to whitelist a file in a password protected location in lighttpd:

$HTTP["url"] =~ "^\/wp-admin\/.*" {
    $HTTP["url"] !~ "^\/wp-admin\/admin-ajax\.php" {
        auth.require = (
            "" => (
                "method" => "basic",
                "realm" => "Password protected area",
                "require" => "user=theuser",
            ),
        ),
    },
},

In your theme’s functions.php add something like the following code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

function mytheme_addmenus() {
	register_nav_menus(
		array(
			'main_nav' => 'The Main Menu',
		)
	);
}
add_action( 'init', 'mytheme_addmenus' );
 
function mytheme_nav() {
    if ( function_exists( 'wp_nav_menu' ) )
        wp_nav_menu( 'menu=main_nav&container_class=pagemenu&fallback_cb=mytheme_nav_fallback' );
    else
        mytheme_nav_fallback();
}
 
function mytheme_nav_fallback() {
    wp_page_menu( 'show_home=Start&menu_class=pagemenu' );
}

In line 1 we add support for the navigation menus. The mytheme_nav() function is what you will use in the theme to display the menu. Inside that function we check if wp_nav_menu() exists, that means if we’re running WordPress 3.0 (or later). If not we’ll use the fallback function mytheme_nav_fallback().

Notice that the fallback also gets called if no navigation menus have been created in the admin area. That’s what the fallback_cb parameter on line 4 does.

To keep the HTM markup and the CSS consistent you’ll have to use the container_class parameter on wp_nav_menu but the menu_class parameter for wp_page_menu.

In your template use the following code to use your new custom function:

<?php mytheme_nav(); ?>

Resources

• wp_nav_menu() reference
• wp_page_menu() reference
• Informative article on nav menus by Justin Tadlock

Ramblings

What’s good about the new menu system:

• Total control over what appears in the menu
• You can add posts, pages, categories and tags in the menu
• Very nice drag and drop interface

What’s bad:

• You will have to teach your users how to use the system properly.
• If you create new pages they won’t be added to your existing menu (except for top level pages).
• You can not control your page menus through the navigation menus interface. I think it is… very very odd that WordPress doesn’t have a simple drag-and-drop interface to arrange pages.
• The previous point means that the new menu system is useless unless you update your theme.
• The wp_nav_menu() call is inconsistent with the existing wp_page_menu() function.

tmp.templateFile = COA
tmp.templateFile {
	10 = COA
	10 {
		if.isFalse.numRows < styles.content.getRight
		10 = FILE
		10 {
			file = fileadmin/template/1col.html
		}
	}
	20 = COA
	20 {
		if.isTrue.numRows < styles.content.getRight
		10 = FILE
		10 {
			file = fileadmin/template/2col.html
		}
	}
}

The ifs check if there is or isn’t content in the right column and the COA returns the correct cObject, FILE in this case.

And then in your main typoscript something like:

page.10.template < tmp.templateFile

instead of the more usual

page {
	10 = TEMPLATE
	10 {
		template = FILE
		template {
			file = fileadmin/template/1col.html
		}
	}
}

That’s all.

# Add a float if we have content in column 2
foo = COA
foo {
	wrap = <div>|</div>
	200 = CONTENT
	200 {
		table = tt_content
		select {
			where = colPos = 2
			orderBy = sorting
		}
	}
	# conditional to test if content exists in column
	if.isTrue.numRows {
		# check current page page
		pidInList = this
		# in the table tt_content
		table = tt_content
		# colPos = 2 (right)
		select.where = colPos=2
	}
}

This example shows a very simple flexible template using a float.

The NIC

Make sure there’s a Linux driver for your network interface card. Make sure the card can be run in master mode.

DHCP

The boxes that will connect need an IP. Install dhcp3-server and do something like this in /etc/dhcp3/dhcpd.conf:

[...]
option domain-name "192.168.6.0";
option domain-name-servers 192.168.6.1;
[...]
subnet 192.168.6.0 netmask 255.255.255.0 {
  range 192.168.6.10 192.168.6.15;
  option routers 192.168.6.1;
}
[...]

Configure the network

Configure the interface so that it can be started with ifup. Usually you want the connected boxes to have access to whatever internet connection the access point has, so I enable forwarding and masquerading in /etc/network/interfaces:

iface eth1 inet static
    address 192.168.6.1
    netmask 255.255.255.0
    network 192.168.6.0
    wireless-mode master
    wireless-essid debianftw
    wireless-key1 s:12345
    post-up /bin/echo 1 > /proc/sys/net/ipv4/ip_forward
    post-up /sbin/iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
    post-up /etc/init.d/dhcp3-server restart

13245 is the WEP password and the network will be called debianftw.

Optional: DNS

You may want to have name servers for the connected boxes. A quick solution is to take those from your /etc/resolv.conf and to put them in your /etc/dhcp3/dhcpd.conf. There are other solutions, like a caching only DNS server.

Security

WEP isn’t a very good encryption but it’s enough for me. You probably don’t want to run this setup for a long time, it’s really just some notes to get me started quickly. Maybe I’ll add more about security in an update.

After some digging I found the problem: 301 redirects don’t pass POST parameters. And when I configured the mailing list I set the domain to nkuttler.de. So mailman sets the form action to http://nkuttler.de/foo/bar, this gets redirected to the correct domain, but the POST data is gone. How do you change the web host? I couldn’t find anything in the admin interface, it looks like you have to do it on the command line.

cd /var/lib/mailman/bin
./withlist -l -r fix_url list -u www.nkuttler.de/

This is the precise command for Debian, on other distros you’ll have to find the correct location.

Update: I’m not quite sure how I missed it, but the host_name parameter should allow you to change this setting as well. For other questions about the default URL you can also read the Where can I change a list or the default URL used for the web interface? FAQ entry.

In the backend, go into the Web->Page view. Click on the small world icon in the tree view (the second column). Click on New. The main column will give you a few choices, you want to create a Page (inside).

After that you will see the page information for your new page in the main column at the right. Uncheck the Hide page box. Fill in some Pagetitle, I like to call my first page siteroot for various reasons I won’t be going into right now. That’s it, click on the save & close icon (a floppy with an x). Great! You have created your first page.

The new page should appear in the tree view (click on the small plus next to the world icon). Then click on your new page, this time click on the name, not the icon. The main colum will show various columns for page content. Click on Create page content of the column Normal. Now you get a list of possible content elements, for now take a Regular text element.

Ok, now it’s time to fill your text content element with some text. In 4.2 you need to click on the Text tab, and the visual editor opens. Just type some random text in there. Click on save & close. That’s it! You have created your first content!

This was all easy I hope. Now comes the harder part of Typo3, working with templates. I’ll take a simplistic approach. I use it in real life as well, but many people prefer using lots of markers or TemplaVoila. Ok, let’s go to the Web->Template section of the main navigation to the left. When you click on the link you should see the option Create template file for a new site. Choose that. If you don’t see it you may not be viewing the template for your first page but for the site.

Typo3 will ask you if you are sure you want to do this, and you’ll tell it ‘Hell yeah!’. You probably are in the Constant Editor now. Select Info/Modify from the dropdown menu. Then click on Click here to edit whole template record.

Here, you see some form fields. One of the is labeled Setup. Delete it’s useless content and paste this code into it:

page = PAGE
page {
	10 = HMENU
	10 {
		# Throw in some primitive navigation
		# This is the first level
		1 = TMENU
  		1 {
        		expAll = 1
        		wrap = <ul>|</ul>
       			NO = 1
        		NO {
        			wrapItemAndSub = <li>|</li>
        		}
        	}
		# Copy the first level to display a maximum of three levels
        	2 < .1
        	3 < .1
	}
 
	# Insert the content from the Normal column
	20 = CONTENT
	20 {
		table = tt_content
		select {
			where = colPos = 0
			orderBy = sorting
		}
	}
}

Then click on the Includes tab. There’s an select field labeled Include static (from extensions): that contains an entry CSS Styled Content (css_styled_content). Click on that entry.

That’s it, save your template! You can go to your site main URL now (not the backend) and see your first content page. One final note before you proceed: When you create new pages, make them all subpages of your first page. You should change your first page to be a shortcut to a page one level deeper that will act as your homepage.

Your next steps should be to read the docs at typo3.org, TSref and the wiki. There’s a lot more to learn.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

foo = HMENU
foo {
	# I use this because I like to have one root page
	# that links to the first content page. All my
	# level 1 Pages are subpages of that page.
	entryLevel = 1
	# define the first level
	1 = TMENU
	1 {
		wrap = <ul>|</ul>
		# Normal Style
		NO = 1
		NO {
			wrapItemAndSub = <li>|</li>
		}
		# Style, if menu page is current page
		CUR = 1
		CUR {
			wrapItemAndSub = <li>|</li>
			ATagParams= class="cur"
		}
	}
	# Define one more level, create a copy of level 1
	2 < .1
	# add as many more levels as you need
	# 3 < .1 etc.
}

Replace foo with whatever marker or position in your TS array you want. If you want to do anything more fancy, you should really read the fine manual.