Christopher J. Hradil

see the socialize plugin in the extend area.

you can either use simple html to link to your image (you will probably need to create a new li inside of an existing ul to hold it, or a new ul li) or you can use a small bit of php in your sidebar to select the correct image if it changes.

unfortunately, you’ll need to start by finding something you can work with in the wp.org extend area, otherwise start creating your own from scratch.

there are really only three things you can do;

1) and 2) change categories or directories so there’s no conflict.

3) add something to the permalink url structure /something in order to eliminate the conflict.

.htaccess and re-writes work by ‘ignoring’ physical files or directories – that’s why they take priority over wp permalinks.

also, wp permalink/re-write functionality is somewhat ‘broken’ by default, example, category permalinks contain /category or some other string in order to avoid these conflicts internally, but this breaks in the case where your /cat/post structure matches either some physical files/directory structure or your wp page/subpage structure, example a page named /cat with a sub-page named /page will ‘break’ permalinks where a category /cat and a post /page for /cat/page.

on most of our wp installations we have altered the core wp code for re-writes in order to eliminate the extra /category part.

we just make sure to manage posts and pages so that the permalinks avoid conflicts. the url’s are much shorter and cleaner this way.

you might consider something as simple as creating a variable for your css classes, then having either the right or left class dynamically update per request, this way you can use one set of code that’s somewhat in line with what’s standard.

looks like a file permissions issue, make sure the sitemap file (and directory it lives in) are both readable and writeable by the webserver.

you might consider changing to an xhtml doctype as a first step, i took a quick look and didn’t notice anything out of the ordinary

it’s possible to do that, but (depending on how many old posts you have) can be a real pain. if it’s a large site your best bet would likely be just re-direct everything to the root of the new site like:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule . http://new.site.url/index.php [L]
</IfModule>

you could also get fancy, and change things to a 301 permanant re-direct, but that’s the easy way. in order to map old posts to new ones you’d need to have a separate rule for each (assuming you’re using some type of pretty/name based permalinks, if they’re /p?## kinds of links anyway, then you could get away with one rule for each type of request (e.g. pages, archives, categories, etc)