New file writing twists
It looks like I've got my file permission issues sorted out now. I case you didn't know, I've moved to a new web host and I ended up having some issues with LnBlog.
My previous host ran PHP as an Apache module. In this configuration, andy files PHP creates are owned by the Apache user. Basically, this means that if you want a script to write to the filesystem, you have to disable safe_mode and make everything world-writable, or you have to use FTP. This is the scenario I had in mind when I wrote the NativeFS file writing module for LnBlog.
My new host, however, runs PHP suexec. This means that PHP is running as CGI, not an Apache module, and is running as my regular user account, not the Apache account. Thus, there is no need to worry about file permissions or ownership, because everything "just works."
Well, almost everything. It turns out that the server objects to scripts and directories that are world-writable, throwing an internal server error. This is a good thing as far as security goes. However, the NativeFS module, by default, makes everything world-writable because it was designed for the mod_php scenario. Hence it doesn't work.
Needless to say, I've fixed this problem and deployed it on my site. Basically, I've just added the ability to set the permissions for LnBlog to use when creating files. I just have to work out the configuration interface and then I'll put up a maintenance release.
You can reply to this entry by leaving a comment below. You can send TrackBack pings to this URL. This entry accepts Pingbacks from other blogs. You can follow comments on this entry by subscribing to the RSS feed.