Perhaps another?

Missing line

File lib/nativefs.php doesn't work without the line

require_once('fs.php');

Otherwise the web-server spits out the fatal error message.

Parameters in fsconfig.php ...

...seem to be hard-wired and aren't modified during installation.

Cannot create blog

Each time I try to create a blog, the software puts its directory hierarchy into lnblog installation folder, even if I explicitly indicate blog path outside of it.

For example, lnblog installation directory is "d:apacheapache2htdocslnblog". No matter how I try to create a new blog in "d:apacheapache2htdocsmyblog" or in "http://myhost/myblog" the thing again puts blog directory tree inside the lnblog installation directory.

Maybe, I'm doing something wrong?

Another problem with paths I've encountered already in v0.3.4, is as follows. The configuration engine inserts part of root paths into root URLs. For example, INSTALL_ROOT_URL for "d:apacheapache2htdocslnblog" would we written in config file as 'http://myhost/Apache/Apache2/htdocs/lnblog/'. The same for BLOG_ROOT and BLOG_ROOT_URL. I had to edit configs manually to make the thing work.

P.S. By the way check out fsconfig.php for ...errr... personal info in the zip you've made available for downloading.

Comments engine doesn't handle backslashes correctly

In my previous posting I've written the path "d: apache apache2 htdocs lnblog" with backslashes and they've disappeared.

Re: Missing line

Thanks for pointing that out to me. I hadn't tested the native filesystem access yet. That one's an easy fix.

Re: Parameters in fsconfig.php ...

I'm not sure what you mean. Yes, the parameters are all defined constants in a PHP file. However, the fsconfig.php file itself is actually *created* by the setup program. If for any reason you need to change the parameters, simply delete the file and when you go to the admin page, LnBlog will ask you to enter the parameters again. The reason I made the parameters constants in a PHP file is that constants are eawsily and globally accessible and that the contents of PHP files can't be retreived via HTTP.

Re: Cannot create blog

Doh, forgot to delete that! Thanks for the heads up. I've updated the zip file. Fortunately, that's just the data from my test server, not from the publicly accessible server, so no real harm done. I guess this is a good sign that it's time to automate the distribution process, huh?

As for your problems, I think I've figured it out. I think your DOCUMENT_ROOT in the userdata/fsconfig.php file is incorrect due to PHP's magic_quotes_gpc setting being turned on combined with the fact that you're running on Windows. Strange, I know, but that's the only way I could reproduce the problem.

Apparently, when magic_quotes_gpc is turned on, the backslashes in the Windows path get double-escaped (don't ask me how, because I don't know yet). You can see this in fsconfig.php - each part of the path is separated by four backslashes, when it should actually be only two (because of the double-quotes that enclose the string). This is compounded by the fact that the stripslashes() function that I used to compensate for magic_quotes_gpc isn't as smart as I would have hoped. It not only strips the extra slashes added by magic_quotes_gpc, it also strips slashes in Windows paths! This doesn't effect UNIX systems and I had magic_quotes turned off on the Windows machine I test on, so I never noticed it before.

I'll have to fix this for the next release. In the mean time, the quick fix is to turn off magic_quotes_gpc (and possibly the other magic quotes stuff) in your php.ini file. If you don't want to do it system-wide, I think you can also turn it off in a .htaccess file.

Re: Comments engine doesn't handle backslashes correctly

Sorry. It looks like this is another case of the stripslashes() function stripping not just the "magic" slashes, but also the slashes in Windows paths. It should start working again once I turn off magic_quotes for my blogs. It's looking like I'm going to have to write a replacement for stripslashes().

Paths again

Yes, I'm running it on Windows. Unfortunately most of the stuff I have to write here is for Windows. :( Got used to and loved Linux/BSD too much when studied in Uni.

So, back to subject. Even if I try and enter my DOCUMENT_ROOT value with straight slashes (d:/Apache/Apache2/htdocs; and that's how it's stored in this case in userdata/fsconfig.php), the described problem with creating a blog persists (new blog directory hierarchy is created in the lnblog installation directory).

Seems like smth's wrong with nativefs plugin. I'm trying to figure out what's up, too.

Hope, you've taken measures to make the info I was talking about an outdated one, haven't you? ;-)

Re: No Subject

Yeah. I was way over-due for a change in that department anyway. And there's nothing like a really stupid blunder to motivate change.

Re: Paths again

Two things on this. First, you should stick to the backslashes, because with the current code, forward slashes will mess up the localpath to URL calculation. Just replace each of those forward slashes with a double backslash in your fsconfig.php and you should be good.

Second, what does the file security on your web root look like? You may have missed this in the readme, but if you're using native file writing, you will need to either manually create the blog directories and set them world-writable *before* you create the blog (so that LnBlog can write the blog files there), or you will have to make your entire web root world-writable (so that LnBlog can create the blog directory). I've noticed that if the blog creation code cannot create the blog directory, then it seems to fall back to the current directory (i.e. the installation root), so that could be what you're seeing. I'm not entirely sure why that is yet, but I'll have to add some error handling code to throw up a message when that happens.