Comments on LnBlog 0.6.0 - No Need for passwd.php

  1. The 0.6.0 package came out with /userdata full of files from your development installation

    It took some time to understand why the installation process didn't succeed as the doc said. /userdata must be wiped out after unzipping...

    • Comment posted on Thursday 14 Dec 2006 at 5:32pm
    • By R. Damon

  2. Crud...

    Why do I always do that? Oh, well. It's fixed now. Thanks for letting me know.

  3. Possible bug?

    After that, I started testing LnBlog, which seems quite a neat project. I'm stuck, anyway, on a strange behavior. After creating a blog, I placed my first entry on it. Comments do work well, but it seems that backtrack and other advanced features (delete, upload and so on) are getting a malformed link, looking like this.
    http://machinename/blogpath/2006/03/ENTRYNAME.phpfunction.php
    If I can understand what you were doing, I believe it should have been like this:
    http://machinename/blogpath/2006/03/ENTRY_ID/function.php
    as each entry seems having its own directory with function files within it.
    At this time, I'm pretty unsure about the cause. At a quick glance, it would seem that lib/blogentry.php's uri function might be malfunctioning or not properly called where needed; unless I have a configuration error of my own somewhere, obviously. Could you give me a hint? Thank you.

    • Comment posted on Thursday 14 Dec 2006 at 5:32pm
    • By R. Damon

  4. OOPS!

    While reporting the URLs I forgot /entries before /2005/03. Sorry. You know, here it's 12.30AM...

    • Comment posted on Thursday 14 Dec 2006 at 5:32pm
    • By R. Damon

  5. Yeah, I know

    Thanks for the feedback. I really appreciate all the help I get on this project.

    I actually already know about the URI problems and have implemented a fix. I've just been busy and haven't gotten around to uploading it. However, a new version is now available from the download page. Thanks for the prod! ;)

  6. OK, keep up with the good job

    Upgraded to 0.6.1. Didn't know you were already aware of that, sorry for bothering. LnBlog is running even too smoothly for its version number, anyway. ;-) Will keep walking up & down to get familiar with the other features. Although a lot smaller than other "blog with database, warp engines and coffeemaker" projects, LnBlog is bigger than it may seem. The only useful thing it may lack (if I didn't miss some of its features) is IMHO the capability to set up a "private" blog, readable only by enabled users. But if it wasn't within the original scope of the project, it doesn't actually matter. I'll probably spend some time on 0.6.1 to understand the mechanism for languages support, too.

    Meanwhile, thank you for everything you're already doing.

    • Comment posted on Thursday 14 Dec 2006 at 5:32pm
    • By R. Damon

  7. Thanks

    Like I said, I appreciate all the feedback I get, even if it's something I already know. It's just good to know there are people other than me who are actually using it.

    Private blogs was not something I ever really considered adding because it's not a feature I would use. However, it's certainly worth thinking about. I was planning to revamp the user security system to include groups anyway, which would integrate nicely with that. In fact, now that I think about it, it's probably already possible to implement private blogs as a plug-in. I'm not sure how well it would work, but in theory it would certainly be possible to block access to the content of posts from all but a given list of logged-in users.

    If you're interested in the internationalization support, I should probably mention that I can use all the help I can get on that. It's essentially untested, owing largely to the fact that I'm the only developer and I speak only English. I'm sure there are still many issues with it, especially when it comes to character encoding.

    Thank you for your kind words. Feel free to drop me a line if there's anything else I can help you with.

  8. Unofficial quick+dirty fix for malformed URIs

    Works in /lib/blogentry.php within 0.6.1; it might elsewhere, too. It took a bit of time to follow the code and see that themes always referred to PERMALINK in order to activate commands.

    // $tmp->set("PERMALINK", $this->permalink() );
    $tmp->set("PERMALINK", $this->uri("") );

    • Comment posted on Thursday 14 Dec 2006 at 5:32pm
    • By R. Damon

  9. Actually, that's another problem

    Thanks for pointing that out. Using the non-pretty permalinks will certainly fix the immediate problem. However, the underlying problem is that the themes should NOT be using $PERMALINK for commands anymore. Do you remember which themes and/or files you had problems with?

  10. Theme using PERMALINK is Terminal

    Yep; see above. I had even forked out a couple of my own versions with different colours (it's so minimal I liked it a lot). If it was just that, then I'll drop it at the next release, restarting from scratch and going on staging with other themes. I do not have LnBlog currently "in production", keeping a blog is just an idea at this time; so, testing is not a problem.
    Meanwhile, I found myself partially rewriting a function in /lib/nativefs.php, in order to have entry deletion working properly.

    function rmdir($dir) {
    exec("rm -rf $dir");
    return true;
    // return rmdir($dir);
    }

    It seems that PHP's rmdir() was called while expecting the directory to be empty, which was not; thus giving back an error. This patch is probably done only in order to match my own modification of the links: in fact, it seems that blog entries stay in the blog/entries/YYYY/MM folder after deletion. They don't work properly, anyway, without their own directory. I've surely forgot to remove the main file, too. :)

    • Comment posted on Thursday 14 Dec 2006 at 5:32pm
    • By R. Damon

  11. Thanks again

    Boy, how did I miss that one? It turns out that the rmdir() error was actually in rmdir_rec(). Somehow I managed to type != instead of == on the check for . and .. entries, so it was ignoring everything EXCEPT . and .., which is exactly the opposite of what I intended. The same bug existed in ftpfs. It probably happened when I switched from calling scan_directory() to opendir(). Well anyway, it'll be fixed in the next release. Thanks for cluing me in on that one.

    And thanks for reminding me to adjust the entry deletion code to remove the pretty-permalink wrapper scripts. That never really occurred to me before.

    As for the terminal theme, I'll fix that in the next release. It only has the one template that needs to be updated.

    Thanks again for all the help!

Add your comments #

A comment body is required. No HTML code allowed. URLs starting with http:// or ftp:// will be automatically converted to hyperlinks.