Comments on: URL rewriting for wordpress and lighttpd http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/ Mostly for myself, but maybe something useful for you too? Thu, 24 Nov 2011 22:48:44 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Nation Pigeon » Blog Archive » VPS Update http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-470 Nation Pigeon » Blog Archive » VPS Update Thu, 24 Nov 2011 22:48:44 +0000 http://emil.haukeland.name/?p=75#comment-470 [...] to (http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/) For getting my permalinks to [...] [...] to (http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/) For getting my permalinks to [...]

]]> By: Pete http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-469 Pete Thu, 24 Nov 2011 22:48:09 +0000 http://emil.haukeland.name/?p=75#comment-469 Thank you kind sir, this helped me get things back on track. Thank you kind sir, this helped me get things back on track.

]]> By: Wordpress URLs with lighttpd | Alastair.pro http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-468 Wordpress URLs with lighttpd | Alastair.pro Tue, 15 Nov 2011 12:22:24 +0000 http://emil.haukeland.name/?p=75#comment-468 [...] so my manual rules need to be re-written and popular CMSs need patches or modifications. Thanks to this helpful post, WordPress as it [...] [...] so my manual rules need to be re-written and popular CMSs need patches or modifications. Thanks to this helpful post, WordPress as it [...]

]]> By: Giovanni Cappellini http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-467 Giovanni Cappellini Sat, 29 Oct 2011 10:18:00 +0000 http://emil.haukeland.name/?p=75#comment-467 Very nice, I think this is the best solution for Wordpress rewrite rules in Lighttpd. Very nice, I think this is the best solution for WordPress rewrite rules in Lighttpd.

]]> By: dof http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-410 dof Wed, 25 May 2011 10:10:03 +0000 http://emil.haukeland.name/?p=75#comment-410 Thanks for this ! Works perfectly Thanks for this ! Works perfectly

]]> By: wordpress rewrite rules for lighttpd « dev.fuzzee.co.uk http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-381 wordpress rewrite rules for lighttpd « dev.fuzzee.co.uk Wed, 06 Apr 2011 22:24:49 +0000 http://emil.haukeland.name/?p=75#comment-381 [...] rules for wordpress/lighttpd and after a very quick google I was taken to an article titled “URL rewriting for wordpress and lighttpd“. Clearly, I thought my search was over. However, I couldn’t help but notice that one [...] [...] rules for wordpress/lighttpd and after a very quick google I was taken to an article titled “URL rewriting for wordpress and lighttpd“. Clearly, I thought my search was over. However, I couldn’t help but notice that one [...]

]]> By: emil http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-294 emil Fri, 11 Mar 2011 17:55:19 +0000 http://emil.haukeland.name/?p=75#comment-294 I believe you're right. What it should mean is that the slash will be included in the param that's sent to wordpress. I'll test this and update the original article to reflect this change. Thank you :)~ I believe you’re right. What it should mean is that the slash will be included in the param that’s sent to wordpress. I’ll test this and update the original article to reflect this change.

Thank you :) ~

]]> By: Nate Eagle http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-293 Nate Eagle Fri, 11 Mar 2011 17:00:40 +0000 http://emil.haukeland.name/?p=75#comment-293 One question: This line: <i># Exclude some directories from rewriting "^/(wp-admin|wp-includes|wp-content|gallery2)/(.*)" => "$0",</i> ...means that accessing, say, wp-admin without a trailing slash doesn't work. (http://yourdomain.com/wp-admin) I just took off the trailing slash in the regex -- any thoughts on whether there are any adverse consequences for this? I can't think of any. One question:

This line:

# Exclude some directories from rewriting
“^/(wp-admin|wp-includes|wp-content|gallery2)/(.*)” => “$0″,

…means that accessing, say, wp-admin without a trailing slash doesn’t work.

(http://yourdomain.com/wp-admin)

I just took off the trailing slash in the regex — any thoughts on whether there are any adverse consequences for this? I can’t think of any.

]]> By: Moving wordpress blog to lighttpd | joe crobak's website http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-252 Moving wordpress blog to lighttpd | joe crobak's website Sat, 15 Jan 2011 22:59:21 +0000 http://emil.haukeland.name/?p=75#comment-252 [...] Add rewrite rules so that most urls in / gets handled by index.php per URL Rewriting for WordPress and lighttpd. [...] [...] Add rewrite rules so that most urls in / gets handled by index.php per URL Rewriting for WordPress and lighttpd. [...]

]]> By: C. Sanchez http://emil.haukeland.name/webservers/2010/url-rewriting-for-wordpress-and-lighttpd/comment-page-1/#comment-248 C. Sanchez Tue, 30 Nov 2010 21:34:58 +0000 http://emil.haukeland.name/?p=75#comment-248 These lines seem to do the trick: url.rewrite = ( "^/(.*)\.(.+)$" => "$0", "^/(.+)/?$" => "/index.php/$1" ) Of course they should go in lighttpd.conf Source: http://www.guyrutenberg.com/2008/05/24/clean-urls-permalinks-for-wordpress-on-lighttpd/ These lines seem to do the trick:

url.rewrite = (
“^/(.*)\.(.+)$” => “$0″,
“^/(.+)/?$” => “/index.php/$1″
)

Of course they should go in lighttpd.conf

Source:
http://www.guyrutenberg.com/2008/05/24/clean-urls-permalinks-for-wordpress-on-lighttpd/

]]>