Its worth pointing out that I made this other developers. If you’re looking for a plug and play solution, this isn’t quite it. But if you’re a developer with the same problem, I’ve done the heavy lifting for you.

How to use:

First make sure you’re not using the default query type (?post=24&blah=foo) style of permalinks.

Suppose you have two custom post types: “book” and “author”. For posts of type “book”, you have: book1. For posts of type “author”, you have: author1.

1. Go to Settings > Custom Permalinks
2. Enter “library” for your slug
3. Drag the “author” block from “Custom Post Types” to “Permalink Structure”
4. Drag the “book” block from “Custom Post Types” to “Permalink Structure”
5. Click “Add New Permalink”

Now you can go to example.com/library/author1/ to read the post named author1 (assuming that the slug for the post author1 is in fact “author1″). Suppose that book1 is a child post of author1 with a similar slug, go to example.com/library/author1/book1/ to read about book1.

You’re probably wondering how you make book1 a child post of author1. In WordPress, you can’t set the parent of a post to one of a different type through the usual methods. So how to do it? That’s up to you to figure out. You can set it manually in the database, but that’s boring. I’d personally make a meta box for the custom post type that serves as the child post (in this case, “book”). In the meta box, create a drop down menu of posts of the type of the parent (in this case, “author”). Reference the functions add_meta_box and wp_dropdown_pages for help doing this.

You might wonder why I don’t do this automatically. I also don’t automatically change the permalink for the posts. Calling the function get_permalink on book1 will just give you example.com/book1/ not our custom permalink. The reason is that you can create as many structures as you like. Use the slug “american” and create a link like example.com/american/MarkTwain/. Whatever you like.

Comment if you need help or have suggestions.

The steps break down like this:

1) Download the latest version from here.

2) Extract and move to /opt/

# tar xvfz xampp-linux-*.tar.gz -C /opt

3) Set passwords for MySQL and stuff

# sudo /opt/lampp/lampp security

4) Only listen for local connections
- Open /opt/lampp/etc/httpd.conf
- Change “Listen 80″ to “Listen 127.0.0.1:80″

You could stop here, but I’m going to make a virtual host (with SSL).

5) I’m going to leave my document root as /opt/lampp/htdocs/ but I’m going to keep all my vhosts in /var/www/
- Create /var/www/
- Let make a wordpress site, create /var/www/wordpress/htdocs/ and /var/www/wordpress/logs/

6) Download the WordPress files
- Move to /var/www/wordpress/htdocs/
- Checkout the trunk from SVN

# svn co http://core.svn.wordpress.org/trunk/ .

I like using svn, because I can quickly do “svn up .” and update my wordpress install. More info here.

7) Create some blank log files

# touch /var/www/wordpress/logs/error_log
# touch /var/www/wordpress/logs/access_log

8) Make your vhost definition

# sudo nano /opt/lampp/etc/extra/httpd-ssl.conf

- Change “Listen 443″ to “Listen 127.0.0.1:443″
- Add “NameVirtualHost *:443″ right below it

- And something like this to the bottom of the file:

<VirtualHost *:443>
DocumentRoot "/var/www/wordpress/htdocs"
ServerName wp.localhost:443
ServerAdmin you@wp.localhost
ErrorLog /var/www/wordpress/logs/error_log
TransferLog /var/www/wordpress/logs/access_log

SSLEngine on
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateFile /opt/lampp/etc/ssl.crt/server.crt
SSLCertificateKeyFile /opt/lampp/etc/ssl.key/server.key
<FilesMatch ".(cgi|shtml|phtml|php)$">
    SSLOptions +StdEnvVars
</FilesMatch>
<Directory "/opt/lampp/cgi-bin">
    SSLOptions +StdEnvVars
</Directory>
</VirtualHost>

9) What’s this wp.localhost nonsense all about?
We need to add a hosts definition

# sudo nano /etc/hosts

Mine looks like this

#
# /etc/hosts: static lookup table for host names
#

#      
127.0.0.1       localhost.localdomain   localhost arch-pc
::1             localhost.localdomain   localhost
127.0.0.1       wp.localhost

# End of file

Obviously you can just keep adding lines for whatever you want. Learn more here.

10) Start up xampp

# sudo /opt/lampp/lampp start

11) Go to https://wp.localhost/ and check out your site!

You might notice that if you try and browse directories with index files (idex.html, index.php, ect) then you get an error, not the familiar directory listing. If you want to change that, open up httpd.conf and add

<Directory "/var/www">
    Options Indexes FollowSymLinks ExecCGI Includes
    AllowOverride All
    Order allow,deny
    Allow from all
</Directory>

Learn more here.

12) Post your troubles in the comments and I’ll do my best to help

Here is the LESS website. The proposed method of using LESS is to write a style.less file and then include less.js which uses javascript to render your stylesheet dynamically. I really don’t like the idea of having to load an extra JS file and then generating the stylesheet on the fly. Talk about unnecessary overhead. But the LESS website loads quickly, even on my phone, so I guess the results speak for themselves. Visiting the page with javascript turned off was disappointing, but not unexpected. Thankfully they also made a command line tool that you can use to compile a .less file into a .css one. Use the compiler for production releases and the JS framework for prototyping. I’ll definitely being using LESS in my next project.

You would write something like this in LESS

@color: #4D926F;
#header {
    color: @color;
}
h2 {
    color: @color;
}

and then get back this

#header {
    color: #4D926F;
}
h2 {
    color: #4D926F;
}

You can even write functions! This code

.rounded-corners (@radius: 5px) {
  border-radius: @radius;
  -webkit-border-radius: @radius;
  -moz-border-radius: @radius;
}

#header {
  .rounded-corners;
}
#footer {
  .rounded-corners(10px);
}

would be compiled into

#header {
  border-radius: 5px;
  -webkit-border-radius: 5px;
  -moz-border-radius: 5px;
}
#footer {
  border-radius: 10px;
  -webkit-border-radius: 10px;
  -moz-border-radius: 10px;
}

This is how CSS should have worked from the start.

sudo nano /etc/apache2/apache2.conf

then went to the end of the file (ctrl+w+v) and added the line

Include /etc/phpmyadmin/apache.conf

All good. Hopefully this helps someone.

2) Extract it

tar xzf eclipse-SDK-3.7-linux-gtk-x86_64.tar.gz

Or just be lazy and Right Click > Extract Here

3) Move to /opt/ folder

mv eclipse /opt/
sudo chown -R root:root eclipse
sudo chmod -R +r eclipse

4) Create an eclipse executable in your path

sudo touch /usr/bin/eclipse
sudo chmod 755 /usr/bin/eclipse
sudo nano /usr/bin/eclipse

copy this into nano

#!/bin/sh
#export MOZILLA_FIVE_HOME="/usr/lib/mozilla/"
export ECLIPSE_HOME="/opt/eclipse"

$ECLIPSE_HOME/eclipse $*

save the file (^O = Ctrl+o) and exit nano (^X = Ctrl+x)

5) Create a gnome menu item

sudo nano /usr/share/applications/eclipse.desktop

copy this into nano

[Desktop Entry]
Encoding=UTF-8
Name=Eclipse
Comment=Eclipse IDE
Exec=eclipse
Icon=/opt/eclipse/icon.xpm
Terminal=false
Type=Application
Categories=GNOME;Application;Development;
StartupNotify=true

save and exit nano

6) Launch Eclipse for the first time

/opt/eclipse/eclipse -clean &

I think its fair to assume that when the University stops supporting Windows XP we can stop worrying about it. See the thing is… wait for it… IE7 can’t run on Windows 7! Internet Explorer 7 makes up 7% of web browsers usage. Come August 1st 2011 Google will officially stop supporting IE7. The death of IE7 might come sooner then you think!