Oh, and you should only need to update fb.php and fb_exif.php.

Just uploaded---http://uncouthyouth.com

Major probs.

Taylor, thanks for responding so fast. Those errors were exactly what I was hoping to see.

I've updated the file again, and this time you should be error free.

Totally messed up on my end, Donald. I just get plain text, no images, and broken links. (I restored the previous version).

Man, sometimes the biggest bugs are the ones that slip you right by. Should be fixed (fb3b04.zip). Let me know if you encounter any more bugs.

Hello, I tried your new version on a small example (would like to use it on my website after).
It seems to work well, and it is easy to go into the codes to change the appearance. It is a great tool, thanks for all your work.
however I did not succeed to add an comment, it gives a lot of error messages ...
Moreover I did not understant what is captcha ?
the example is here :
http://mathildedn.free.fr/essai/fb.php

Just to let folks know, there's a small bug in "fb.php" in the "fb3b04" build. On line 407, where $fbpostform is defined, go right to the end of the string and find:

value=\"{$fbimage[0]}\">

This is an improperly closed <input> statement, which is invalid XHMTL. It should be:

value=\"{$fbimage[0]}\" />

This bug only shows up when using the post form, and while it won't break the page it won't validate.

hi elwing,
hi all the others,
i added your tips regarding doctype and mimetype into the folderblog-wiki (hope you don't kill me for doing so :-/ )
...and also updated the gzip-compression article for both fb2.02 and fb3 (beta)

btw: donald, could it be you made fb3 now work with a "old category-folder-environment" because it seemed to me the first beta-release couldn't handle the zero-byte-files (giving errors on image-dimensions - that of course were unGETable from these...)

I solved my problem ....
sorry :)
keep up this good work :)

No problem, Erik, though I might want to update that section, both on the wiki here and on my site, to make the thing a little more comprehensive and acurate (the 'template_comments.php' also needs to be edited in Folderblog 3, for example). Plus, it might be a good idea to credit everyone involved on the wiki, rather than just me! I'll sort this out a little later on.

Just an added note, the link to download 'gzip-compression.zip' results in a 404 error (though the link to download the test file works just fine).

Donald -- the beta "4" plus Elwing's modification works for me but I still have that weird effect with the trailing "/". Compare the following URLs:
http://www.photosensitive.ca/folderblog/fb.php/ with
http://www.photosensitive.ca/folderblog/fb.php

Jordan, I think I know what the problem is, but I'll need to look at your _SERVER variables. Can you create a file called info.php in your folderblog directory that contains

<?php phpinfo(); ?>

?

Donald -- done -- go to
http://www.photosensitive.ca/folderblog/info.php
it's all Greek to me!

Jordan, thanks. I tweaked the code a bit based on the info, though I'm still not sure I've nailed it — let me know if fb3b05.zip works for you (all you need to update is post.php).

post.php? I mean fb.php, of course.

Minor Problem:

When using <#fbcats#> in a template file (like in the standard template) and switching off the category option in the fb_vars.php ($include_cats = 0;), the fbcats-function returns a single <ul> without a closing tag, which results in a XHTML validation error.

While on the subject of the <#fbcats#> tag, it might be an idea to enclose the "(show all)" link in something like a <span> tag or such like, and give it a CSS class or id name. As it stands, this works just fine for the default template, but it's a real pain for template designers to work round the problem of placing this "(show all)" link without hacking the fb.php file.

Better yet, you could put the "(show all)" link inside the first <li> tag, so it flows with the other catagories listed. While the default template might need to be edited, the end result would be something that template designers wouldn't need to address.

Donald -- the URL "/" problem is fixed now -- you can have a look (http://www.photosensitive.ca/folderblog/fb.php)
When clicking back through the pictures, should the picture name show up int the URL like it does?

Actually, another thing -- when I moved the folderblog files to my main web directory, everything "broke". Could this be because of where <#fbdir#> is defined? I don't see it in any of the settings files, and I know it determines where FB looks for the style sheet (I removed the reference to fbdir in the template files) but I'm afraid I've messed things up more! Have a look:
http://www.photosensitive.ca/fb.php
and click around...
Eventually I'd like to re-name it as index.php just as with my FB2 installation.
Thanks Donald!

Jordan, the <#fbdir#> reference has to be in the templates (<#fbdir#><#fbimage#> and <#fbdir#>style.css) because it provides an absolute link — with a relative link, the browser is looking for the nonexistent image or CSS file at fb.php/image/IMG_123/style.css (for instance).

(And yes, image names are supposed to show up in the URL.)

(Elwing, I'm working on your suggestions. I'll post an update shortly.)

Mathilde, I'm not positive what your error is, but I think I may have snagged it. Try the new version when I release it later this afternoon.

A captcha is a spam-prevention measure that requires the user to input the text displayed in an image. You can read more about it here.

erik, the old directory structure (the 0-byte files) for categories will not work with FB3 — changing this is something I'm looking at, but I simplified the categories system so the average web-knownothing could use them.