Be Technical by Techniques

I love you. Er.. I mean, thanks for the script.

I’m having WP 2.5.1 and Lighttpd on debian etch, and I’m having some questions to this interesting post:

Where do I put this code:

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

I enabled mod_magnet, but a restart of lighttpd gave me this:

Starting web server: lighttpd2008-05-19 19:49:14: (plugin.c.165) dlopen() failed for: /usr/lib/lighttpd/mod_magnet.so /usr/lib/lighttpd/mod_magnet.so: cannot open shared object file: No such file or directory
2008-05-19 19:49:14: (server.c.594) loading plugins finally failed

I’m obviously missing the main part here

Please guide me in the right direction.

/ Denbert

I just migrated from apache to lighttpd and thanks to your help my wordpress site works like a charm, AFAIKT

What do I have to do when Wordpress is in a subdirectory like ‘www.example.com/blog/’?

@Jani - that was because of “wptexturize screw up” ; for some reason WP converts all opening double quote to “ & closing double quote to ” Anyway, this is fixed now in my WP setup, and I confirmed that double quote works well in lua

@wil - simplest would be to keep everything same except following line

lighty.env["uri.path"] = "/blog/index.php"

or better would be something like this (not tested so please don’t kill me if this doesn’t work)

Content of /etc/lighttpd/lighttpd.conf

$HTTP["host"] == "dev.sudhaker.com" {
  server.document-root = "/sites/sudhaker.com/htdocs"
  $HTTP["url"] =~ "^/blog/" {
    magnet.attract-physical-path-to = ( server.document-root + "/blog/rewrite.lua" )
  }
 
}

And content of $WP_ROOT/rewrite.lua

attr = lighty.stat(lighty.env["physical.path"])
 
if (not attr) then
  lighty.env["uri.path"] = "/blog/index.php"
  lighty.env["physical.rel-path"] = lighty.env["uri.path"]
  lighty.env["physical.path"] = lighty.env["physical.doc-root"] .. lighty.env["physical.rel-path"]
end

I just set this up and it is the only 100% perfectly working setup that I have seen. Alot of mod_rewrite setups get close but interfere with other folders not related to wordpress. This one allows my phpmyadmin install to co-exist and does proper rewrites. Thanks!

I did a performance comparison between mod_magnet and mad_rewrite based solution. Results are posted at following URL

http://sudhaker.com/web-development/lighttpd-modules-compared-mod_magnet-and-mod_rewrite.html

According to my basic testing results, mod_rewrite is slightly better performing than mod_magnet.

FYI: I’ll continue using rewrite.lua because performance hit is not significant and it provides more reliable and consistent solution.

Cheers,
Sudhaker

@Denbert
You needed to install the lighttpd-mod-magnet package in order to enable mod_magnet.

@Sudhacker
I used the mod_rewrite way and it make a mess on the index files when using subdirectories.
I’ve been trying to use the mod_magnet you wrote on a site.org/user/blog, but i only get 404 error :-/

Here is how i have done it: http://switnet.dyndns.org/ark/pmwiki/pmwiki.php/Varios/Wordpress-URL

(if you would like to edit, just let me know)

I used the mod_rewrite way and it make a mess on the index files when using subdirectories.