joel01

Kafkaesqui, you’ve made my day! Thank you for your code, I adapted it to suit my needs.

@usuario:
Make sure you insert any additional ‘if’ statements before the ‘posts_where’ function returns. You should be able to use as many as you like for any number of situations. Just make sure you follow the format of the examples listed on the Conditional Tags page that Kafkaesqui linked to.

I’d like to know how to do this without a plugin. The Loop entry in the codex says the following about excluding categories in The Loop:

Please note that even though the post is not being displayed it is still being counted by WordPress as having been shown — this means that if you have WordPress set to show at most seven posts and that two of the last seven are from Category 3 then you will only display five posts on your main page. If this is a problem for you, there is more complicated hack you can employ described in the Layout and Design FAQ or you can use query_posts if you only need to exclude one category from the loop.

However, the Layout and Design FAQ doesn’t seem to mention this complicated hack. Would anyone know what it involves?

What I did was to use the following template tag and options in my sidebar.php:
wp_list_bookmarks('title_li=&categorize=0');

I’ve found a solution. It uses externals definitions, the same way plug-ins are handled if you install WordPress via Subversion. This allows any number of sub-directories in your local repository to be associated with different remote repositories.

First, import your custom folder (whether it be a theme directory or whatever) into your own remote repository. Remove this directory from your local WordPress directory structure.

Now you need to declare that this same directory (now deleted but soon to be checked out) is to be managed externally. Change into into its parent directory and run:
svn propedit svn:externals .
An editor window should open (this assumes that you’ve set some kind of EDITOR environment variable in your shell).

Externals definitions are defined as follows:
<sub directory name> <URI of external repository>
Save and close.

Now try running svn up. The custom sub-directory and its original contents should be recreated.

It took a lot of fiddling around for me to get it working smoothly, just make sure you backup any important custom files first before trying. One thing I’ve noticed is that you need to be inside your sub-directory when committing changes for it. If you try svn ci in any directory above it then it will complain that you don’t have permission to make those changes to the remote WordPress repository (well it did for me but I’ve checked out a stable tagged version).