I can test it...I've the space...but I don't know any programming so if your expecting any exact technical feedback I might not be the person for it. In any case do let me know. And it would be just great if you could implement that function of having archives that can be sorted by month and year...it is pain to load a page full of hundreds of thumbnails...as I don't like to have multiple archive pages.

Dont worry, that will be one of the next functions I am working on.

You can download the new fb.php at

http://www.ikue.de/blogme_barcelona/fbikuereloaded.zip

Put the fb.php in the main directory, and if you want to use any EXIF functions on your pages also put the fb_exif.php into the Extensions directory.

I dont have to mention that there is no bad code or anything in the archive. I will add new functions in the next days, also (or especially) with regard to error handling as all the dubious error messages of the current fb release are really stupid!

Have fun with it!

ikue,

Just tried this at my site to see it. It was not able to display my captions or comments from my fb3 site. I am using the almanac template.

richard

Great! Downloadng it now...will install a test gallery with it over the weekend and let you know how it goes!

Richard, tell me, what exactly happens, any messages or alike? Usually nothing should happen as I primarily extended the functions of fb.php and included some better error management. Do you have an URL where I can see the result?

In general, if anybody has questions how to use the in a post above mentioned new functions, tell me! I wrote comments in the new fb.php to explain the changes.

I have the aim to develop a new stable version of folderblog by which we can avoid 90% of the forum discussions, because the program will automatically tell you what has to be done. ;) A vision...

Ikue, I installed a test blog and tried your reloaded versions. It is working perfectly. Haven't had any problems till now!

ikue

No error messages. Just no comments or captions show up after replacing the fb.php and exif file with your new version.

I'll leave the new fb file up for a few hours but I hate not having comments/captions.

http://www.blankmindfotos.com

Ah Richard I know your problem. The orginal version of fb3 uses a very "unlucky" method of referring the images, resulting in its total inability to load more than just one file extension (e.g. jpg).

Basically, your comments are still perfectly there, the new optimized fb.php just doesnt find the old ones. ;)

Dont worry, I will create a little script that solves this problem completely.

Anil, I am happy about that! ;)

Thanks for checking this out... I will revert to the old file so visitors can view the comments/captions.

richard

Can you tell me how to change the exif for my focal length to only show as #.# instead of #.#####

Focal Length 4.000000 to
Focal Length 4.0

Tell me about the "Name" of your camera, so the one that is given by the EXIF functions, then I will include an appropriate source code in the next release of my fb.php

folderblog ikue release 1.1 available

http://www.ikue.de/blogme_barcelona/fbikuereloaded.zip

* you can hide the "show all" link on the categories menu by adding "$hideshowall=true;" to fb_settings.php

* backward compatibility of comments, they are now shown even if you used the old folderblog beta before. just write "$enable_compatibility=true;" to fb_settings.php

Note, I could not test all functions intensively, you feedback is highly welcome!

ikue,

I use two different digital cameras, both Canon, one is the G3 and the other is the S410.

I'll d/l the new file and report back here.

thanks

Still I need the exact strings that folderblog, or the EXIF function, gives you so I can program appropriate lines into the next folderblog release. Otherwise I cannot let the cameras be recognized.

ikue,

just installed ikuefb1.1 and captions appear but my comments are not appearing. I did add the $enable_compatibility=true; in my fb_settings.php. I'll leave it as it is for you to look at if needed.

thanks again

ikue

my cameras are recognized but the focal length looks like this in the information section of the web page:
Focal length: 4.01234 instead of a shorter version like:
Focal Length: 4.0

sorry if I misunderstood your request... :-)

I know, this is clear - but I need the exact camera names resulting from the EXIF functions so I can write a source code like IF CAMERA=BLABLA THEN DIVIDE FOCAL LENGTH BY XXX

PS: are you sure the captions dont appear? I can see some text below the image

ah sorry there are two types of comments in folderblog. The captions plus subtitles function now, good. I will take care of the other regular comments that visitors can make tomorrow or Monday.

hi ikue,

thank you for response: I replaced your php-files with mine on the ftp-server, and renamed the old ones. resulting in a blank page: "http://tomasio.at/kraxfotos/fb3/fb.php"
the old fb3 showed at least some photos:
"http://tomasio.at/kraxfotos/fb3/fp_orig.php"
I think I will have a chat with my host provider if they can include this image resizing server extension.

ikue,

Oops.. Actually 3 cameras. If I understand you need the exact name used in the "Information" section used by FB? If correct, here they are listed below.

Canon Powershot S410
Canon Powershot S100
Canon Powershot G3

thanks... richard

Hola Richard,

I made the necessary changes in the exif extension module which you can download at
http://www.ikue.de/blogme_barcelona/fbikuereloaded.zip

Please tell me whether it works.

Además, I just fixed the issue that regular comments did not show up. fb ikue reloaded 1.2 ready for testing. ;)

Excellent!! I have captions, comments and a shorthand version of the focal length in mm's.

thank you for your patience and hard work ikue.

richard

You're welcome!

folderblog ikue release 1.4 is out (dont ask me where 1.3 is gone ;) ), among others the following changes:

* create_uploadtitles=true; in fb_settings.php will automatically give titles to every uploaded image, according to its filename
* stupid rss error message should have disappeared
* some important internal restructuring, I am preparing a per user filtering function

http://www.ikue.de/blogme_barcelona/fbikuereloaded.zip

Have not tried 1.4 yet, still using 1.2. But if I set $sort = 3 then I get these errors:

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 269

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 272

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 269

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 272

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 269

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 272

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 269

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 272

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 269

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 272

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 269

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 272

Notice: Undefined index: DateTimeOriginal in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 269

any idea what is happening?

richard

Yes I think so... will take of that tomorrow.

The problem is in those lines where the EXIF sort is done. The reason might be a specific setting of your server configuration. Please download fb ikue 1.5, I added some new error management which might solve the issue. I need your feedback to see whether it works now.

Here we go! folderblog ikue release 1.5 is ready.

* pictures can now automatically be resized on upload!
$resize_on_upload=true;
$upload_maxwidth=300;
$upload_maxheight=300;
add this to your fb_settings.php, and you will enable this great new function. ;)
* better error handling in the creation of the RSS feed
* some internal improvements like more intelligent error messages ;)
* also the EXIF extension has now less errors, update it!

http://www.ikue.de/blogme_barcelona/fbikuereloaded.zip

Please give me feedback whether it works also on your webspace.

Be aware of one thing I just found out, currently EXIF information is lost during the image resizing. Please wait for a fix if you want to use this function.

Dear... it seems that including a complete new library into folderblog is the only solution for this.
http://www.zonageek.com/software/php/jpeg/index.php
There seems no short source code available to transfer EXIF information. Anybody disagreeing?

After some intensive hours of work I finally could solve the issue, download at
http://www.ikue.de/blogme_barcelona/fbikuereloaded.zip
and make sure you put all extensions into the right place. Plus, a new function:
* You can now delete individual images very comfortably from the "post" admin menu (where also title etc. can be entered)

ikue,

so far so good. $sort=3 is working like a charm! Any way to add ability to add a resize radio button for 640x480, 800x600,1024x768 and "NO RESIZE" to the post page like you did with the "delete radio button"? Users could add these separately or all at a time and click the radio button they want to resize their image to as they posted it.

Going to test post and resize now.

richard

ikue

Uploaded 1.5 and added

$resize_on_upload=true
$upload_maxwidth = 640
$upload_maxheight = 480

to my fb_settings.php, then tried to view my site and got this error:
Parse error: parse error, unexpected '=' in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb_settings.php on line 12

On line 12 this is the setting: $resize_on_upload=true
that is erroring out.

Please add the always necessary semikolons (;) to each line´s end, then it will work ;)

dang it! should have noticed that...

Ok, fixed that and tried to upload a file. It seemed to be working and then I got this error:

Notice: Undefined index: deleteimage in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 557

Checked folder, and didnt see the new upload.. Any idea's?

richard

Try replacing the line
if ($_POST["deleteimage"]=="yes") {
by
if (@$_POST["deleteimage"]=="yes") {

So, adding the @ in front of the POST variable. I am sure this will do it. Tell me, then it will be amended in version 1.6.
Just for explanation, PHP is quite sensitive whether variables have been created or not, and if you dont tell him to delete (which creates variable POST["deleteimage"]) the error message occurs.

That fixed the error but it does not upload the file I browse to on my hard drive. It doesn't appear to do anything.

Granted I never used upload from the post form because so many images needed to be resized I would do that before I uploaded in Ws_Ftp app.

Suggestions?

richard

Okay another hint which might help: the original folderblog 3 is quite... well... lets say, sensitive with regards to file extensions. It can only show one, which is quite stupid especially if you consider that for a linux server the extension ".jpg" is NOT the same as ".JPG" or ".jpeg".

After quite some hours of work (as it was influencing 90% of the whole source code) I could fix this. Just change the normal $file_extension setting in fb_settings.php to

$file_extension = array(".jpg",".jpeg",".gif",".JPEG",".JPG",".png",".PNG");

By the way, you should check via normal FTP access whether the filename you uploaded appears in your photos directory. If it is there, the issue can be solved with the above mentioned setting. If not, we will see further.

however, if you know you won't need all those extensions, how much better would it be to take the unwanted out in terms of the speed at which the script will run?

Of course the line is an example! I shall just show the format in which file extensions can be entered. And with regard to your thoughts about speed, I did some benchmarking and there is definitely nothing to worry about. It is a highly useful extension which can be enabled on demand.

ikue

If i use WS_FTP to upload to my server the file name remains unchanged from my desktop to the server dir? Was that what you wanted to confirm?

If I use the post operation (http://www.frhendrix.com/folderblog/fb.php?p=post/) in FB3 and choose to use the "or upload a new image" browse button, FireFox acts as if something is happening but I see no progress bar activity and then I ge the "Update Successful" message but no new file is uploaded. Also, no errors are generated. Am I doing this correctly?

No, what you are supposed to do now is to take your WS_FTP program, open the connection to your website, and look there into the photos folder. Dont forget to hit the refresh button so the content is really up-to-date. Look there for your uploaded file. If it is there, everything is fine and you just have to amend the extensions variable in fb_settings.php

ikue,

yep, tried that several times. Nothing. It doesn't look like FireFox does anything. I have even checked to see if it is uploading to a different DIR. Nothing.

To review:

I access Fb3 with fb.php?p=post/ there is an image there I could update if wanted but I choose to 'browse' to file (file is 2.5mb, does that matter?), enter PW, click 'update' and wait. FireFox seems to be whirling about for about 15s and states 'update successful'.

I refresh WSFtp and see no new file. Check all DIR's and no new file was uploaded.

richard

Is there any place in the upload code I could specifiy a path to upload the file to in fb.php?

Of course there is a place, in
move_uploaded_file($_FILES['uploaded']['tmp_name'], $newuploadedimage);

To get more insight into the specific problems with your server, it would be necessary to check where the php stops, so whether it gets to the above mentioned line or not.

ikue

do you have an email address so I can contact you personally?

Update on uploading with fb. Browse to file, enter pw, click update, browser then returns Internal Server Error 500. Refresh in browser does not show uploaded file. In WSFtp I see file is uploaded to DIR but not resized.

I have

$resize_on_upload=true;
$upload_maxwidth = 640 ;
$upload_maxheight = 480;

in my fb_settings.php file.

any suggestions?

thanks

richard

put a "bjoern" in front of the domain "ikue" and add a ".de" at the end, then you have my email address ;)

About the 500 error, check Google for a better understanding.

folderblog ikue release 1.6 is out!

http://www.ikue.de/blogme_barcelona/fbikuereloaded.zip

Changes deal mostly with some bugfixes, especially about the image upload / delete functions. Richard, this might solve your problems, it is worth a try. I included all changes we discussed since the last release.

ikue

Downloaded and installed 1.6. Tried to upload a image and got this error:

Notice: Undefined variable: Comment in /mnt/web_g/d03/s49/b021eca5/www/folderblog/extensions/fb_exif_extended.php on line 697

Warning: Cannot modify header information - headers already sent by (output started at /mnt/web_g/d03/s49/b021eca5/www/folderblog/extensions/fb_exif_extended.php:697) in /mnt/web_g/d03/s49/b021eca5/www/folderblog/fb.php on line 551

richard

Interesting, this is not about fb but about the EXIF extension.

Go in fb_exif_extended.php to the line with the content
for ($a=2;$a<$length;$a++){

and add the line
$Comment="";
BEFORE it. Then try to upload again and tell me what happens.

The error seems to occur because you tried to upload a JPEG with comments, a format I dont use during testing.

@ Richard, did it help??

Generally: Some minor bugfixes in ikue reloaded 1.7
http://www.ikue.de/blogme_barcelona/fbikuereloaded.zip

AND: you can force fb to show a regular 404 error if somebody attempts to load an image that doesnt exist on the server. Enable it in fb_settings.php by
$show_404_message=true;

I will not develop further on this project as I dont see a legal base for it, see my other post in this forum. As long as we dont have a permission by Tetto, it is not worth the effort.

i replaced my index.php file with the fb.php file and i get this error:

Warning: main(fb_settings.php): failed to open stream: No such file or directory in /htdocs/www/index.php on line 18

Fatal error: main(): Failed opening required 'fb_settings.php' (include_path='.:/usr/local/lib/php') in /htdocs/www/index.php on line 18

also just wondering what exactly the 404 code in fb.php does:

will it produce a 404 error if requested for an image that used to be on the server but is now no longer accessible?

ok just added require_once("fb_vars.php"); to the file and it works.

but now i get all these errors after my page loads. where are these variables defined?

Notice: Undefined variable: use_alt_url in /htdocs/www/index.php on line 26

Notice: Undefined variable: locale in /htdocs/www/index.php on line 351

Notice: Undefined variable: time_difference in /htdocs/www/index.php on line 352

Notice: Undefined variable: emptylink in /htdocs/www/index.php on line 787

Notice: Undefined variable: fbblogtitle in /htdocs/www/index.php on line 842

rohan, you really need to understand php scripting to pull off this customization. If you change file names around and don't know how to adjust the scripting, you can cause errors, which is what you're doing.

It appears you changed the file fb_settings to fb_vars (or perhaps ikue did that, and should be blamed for confusing people) and now the code needs to be fixed.

And yes, theoretically, fb can be programmed to return a 404 error if it does not find an image. If and when the great Tetto returns to this space, an official new release can be made to solve these problems.

Guys, simple issue: Rohan obviously tried to install a new fb3 file over an old fb2 installation. This does not work as many required variables, path names etc. changed. You will find details in the installation manual on this website to fix the major problems.

@ Geoff: My development is not about confusing, it is about enhancing...

@Rohan: Additionally, the action you have taken (replacing your own index.php with another new fb.php) is generally an absolutely valid process, and usually works fine with any of the last releases. Just make sure it is based on folderblog 3.

And finally a comment on my 404 extension: Normally, if you ask folderblog 3 via parameters to open an image that does not exist it will automatically forward you to the last picture in your archive, without displaying any error or comment on this process.

Search engines and users might be confused about this, so I added a regular 404 error page if you attempt to open a nonexistent picture. You can optionally enable this function by "$show_404_message=true;" in fb_settings.php.

ikue

been offline for a while. my 14 yr old had a battery blow up in his face... it was touch and go for a while that he may lose sight in his right eye but things have worked out for the good... As soon as I can get caught on things around here I'll try out the new version.

richard

Richard, dont worry about fb, I understand perfectly your priorities! I hope all the best for your child, we'll stay in touch.

Hey folks, I am about to launch folderblog ikue reloaded 1.8 which has a major extension that allows automatic filtering of images by keywords which in turn have to be stored in your EXIF data of the jpegs.

Has anybody suggestions for a comfortable software to access (read/write) comfortably EXIF data of a large sum of files without having to enter something for every single one?

The function is gonna work like the concept of e.g. gmail, so a "tagging" of files. Plus, I found some ways to make it really impossible to access the images otherwise via the webinterface, for example by changing URL strings or something.

ikue, I just wanted to thank you for all your work. I needed a simple web-based gallery package, and discovered folderblog yesterday. Got it all set up and integrated with a client's existing website, and then realised there was no easy way to delete photos! Your reloaded version saved my ass :) Thanks!

You're welcome ;)

Any updates on this? The URL to download no longer works

Thanks to Donald Tetto´s license policy it is not allowed to build modified versions of fb, therefore I currently dont develop on it, no. You know who to blame for it.. ;)

*sigh*

Yes, maybe *sigh* is the right statement. Ikue, Erik and others are trying to get most out this marvelous photoblog-script by donald and share their knowledge with others. Questions are answered by the same 2 or 3 people over the last month. And all we got is a "wassup" on january, the 7th.

What should I say? *sigh*

das wir doch ich du nase :P

I already thought so. ;) It would have been a bigger surprise if donald had shown up...

Trotzdem, wie steh ich jetzt da? ;-)

Erik, DU bist die Nase. :p

und ich dachte dir wär klar, dass es hier nur ikue, mich und dich gibt .... bwuahaha

(den lacher wars wert :D)

man könnte es manchmal fast meinen, ja... ;)

du ich will grad ne install routine schreiben zwecks der htaccess (simple datei - hole infos aus den _settings und generiere die htaccess in eine textarea für copy&paste)

einen ersten entwurf für das stylesheet hab ich (is aber noch nix ganzes...)

wenn du dazu noch ein paar ideen hättest, oder tips ;)
ich könnte mir das auch so ähnlich vorstellen wie bei wp. step1 -> step2 -> done.

vllt. magst dich ja einbringen...

man könnt zb noch prüfen welche setlocale() schreibweise ein server will, prüfen ob schon bilder in ordnern etc...

theoretisch könnte man alle _settings oder sprach-relevanten dinge abfragen oder eingeben lassen... was meinste?

What exactly do you intend to do with the .htaccess (I will stick to English as we have many international visitors here...), e.g. what functions do you want it to provide?

Generally speaking it is a nice idea creating an installation routine. I will help you if I can.

A thing I am currently working on in my folderblog ikue release is the ability to even upload and display videos in fb.

An installation-routine would be a great idea. I have a new version of almanac ready with "really" short urls, comments working fine now and so on. For the short-urls without that "image/" thing, there is only the way to modify the fb.php (index.php). If I can't provide a ready-to-install version (license problem :rolleyes: ), it would be a handy alternative to use a install.php which could do the necessary changes right on the server.

I'm really in the mood to write a new template as well, so lets try something like a "setup-routine".

Jowra, can you post your changes you made in fb.php so I can include them into a new version of fb ikue reloaded? Just for the case that Donald might return one day and keeps his promises... ;)

If one just want to remove the /index.php/ from the url, this is no big deal. Simply change the function linkPrefix() at line 166 in fb.php from:

function linkPrefix() {
global $fbfile, $post, $category;
return "$fbfile$post" . rawurlencode($category) . "/";
}

to

function linkPrefix() {
global $fbdir, $post, $category;
return "$fbdir$post" . rawurlencode($category) . "/";
}

Beside that, $use_alternate_url must be set to 1 in fb_settings.php and you must use this .htaccess code:

------------------------------
Options +FollowSymlinks
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} -d
RewriteCond %{REQUEST_URI} !/$
RewriteRule ^.*$ %{REQUEST_URI}/ [R,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d [OR]
RewriteCond %{REQUEST_FILENAME} /photos$
RewriteRule ^(.*)$ index.php?p=$1
-------------------------------

where /photos/ is the directory in which folderblog is installed.

This works pretty good in all cases (with or without categories and so on.). It becomes a lot more complicated if you want to remove the /image/ from the address.

In my photoblog I must change some more lines in fb.php to achieve that (its not much and if you're interested I'll post it), but this only works if you're not using categories (as in my case).

At the moment I'm trying to find a solution which even works with categories, so that images that are in the folderblog-root have an URL like this:

/folderblog/one_photo_example/

and image that are in subdirectories are looking like this:

/folderblog/holiday_in_paris/next_photo_example/

But this /image/ thing is everywhere in fb.php. ;-) I think donald used it as a pseudo-category, but in my eyes this makes things like url-rewriting much harder, then it should be.

nun: eigentlich wollte ich auch an einem theme arbeiten, bin aber erstmal bei den admin-zeug hängen geblieben.
da es aber eigentlich unsinn ist die admin-optionen in einem theme abzulegen hab ich mal mit den farben dieser fb.org-seite gespielt.

ich hab nen screenshot hinter den link unter diesem post gelegt. so oder so ähnlich simpel könnte man die install-routine machen...

ich stells mir so vor:
1) ich lade ein zip hoch, indem alle dateien sind.
2) rufe install.php auf. dieses skript schaut nach, ob ein wert $install=="done" auf done steht. falls ja -> abbruch mit hinweis: "install.php sollte gelöscht werden.
3) ansonsten: chmod der ordner und dateien,
passwort für fb-festlegen, und den pfad sowie vllt. noch die sprache auswählen und setlocale testen (es gibt ja de_DE@euro, de, ger, deu, german, de_DE etc. das scheint server-abhängig zu sein) abfragen. alles in settings schreiben. fertig.

4) nun sollte fb sagen: "alles ok, fertig" in einer textarea die htaccess zum copy & paste anzeigen und schließlich auf /post/ verlinken, (wobei ich post in admin umbenennen würde) dabei wär sicher auch wichtig, dass fb auch ohne htaccess noch funzt.
im zip sollten 1, 2 sample-images sein, damit fb gleich funktioniert (dazu müsste man zwar die ordner auf photos, thumbs etc. festlegen)

man sieht also ein sample-bild und hat auch gleich das admin-panel vor sich, liest, wie man dieses erreicht, was es kann, kann gleich eigene bilder hochladen, etc. (mit link zur frontpage, zum forum, etc.)

mal sehn wie ich dazu komme, aber werd mir design-mäßig mal etwas schlichtes überlegen.

( ps: der clou, meines admin-panel ein leicht transparente liquid-width box, die sich über die seite legt, position fixed lässt sie stehen und werd noch ein toggle-position js einbauen, damit es je nach theme nicht das verdeckt, was man uU grad bearbeiten will :-)

pps: though i speak english very awful ;) as native german-speaker i prefer to not speak english, so dont blame your deutsch-skills on me ;)
(i alsways feel uncomfortable in english, wie ein sprachzentrums-spasti because insecure bla bla ...

ps: ich hab das url rewriting mit fb2.02 jetzt halbwegs gelöst, weil es dort diese dämliche ?image/category-schreibweise nicht gibt ist es bedeutend einfacher. es ist aber noch viel arbeit, fehlende funktionen hab ich eingebaut aber, die konditionellen dinge machen mir probleme, denn ich will das datei-handling auf das von v3beta umbauen.

ps: wer den admin / post-bereich aufruft sollte auch ncoh folgende infos sehen: chmod der ordner test bzw. ein kleines ok-symbol, weil das ja sehr oft hier im forum zu problemen führte.

alle sprachspezifischen dinge sollten entweder in eine fb_en.txt oder fb_de.txt wandern, wie seht ihr das? ist das mit euren themes machbar? sprache ist ein kompliziertes thema, aber vielleicht finden wir ja ne gute lösung dafür.

greets to all folderbloggers :)

Nice ideas Erik. I thought about localization too. Another point is: html-possibilities in the comment-fileds.

There could much be done, maybe in a team. But that all would require somewhat like a GPL for folderblog. :-(

*sigh*

pps: nochwas zu rewrite, ich hab bei meinem noch eine variable eingebaut, die auch suffixe ermöglicht. also urls nach dem motto: /categoryname/imagename/ oder categoryname/imagename.html je nach dem wie dann diese variable setzt müsste sich auch die htaccess ändern. (deshalb auch die notwendigkeit eines installers - zuviel editieren wird schon recht unkomfortabel)

>> There could much be done, maybe in a team. But that
>>all would require somewhat like a GPL for folderblog. :-(

not as long we are alone in here ;)

i think we should first start doing something, if he cares about future of fb3 this could bring him back on the scene ... *doubblesigh* :)

>>html-possibilities in comments

yeah, something like:
preg_replace(array(':)',':D'),array('<img src="smilie1.gif">', and so on...

but thats all kind a too advanced for my coding skill...
... i hope to cope with urls in the first place...

Wow. I think we're messing this thread up, but I just found out, that you can easily use the following declaration for the theme:

$template_name = "templates/almanac/almanac";

that means, an fb-installation with more then one theme could easily be packed and the directory-structure is still uncluttered. :)

http://www.minigal.dk/
there localisation is solved very nicely, download your languagefile. done. why fb hasnt this already? are we lazy?

shice, all der aufwand, aber ich glaub ich switch zu mg2. viel zu komfortabel. viel zu viel aufwand einen ähnlichen komfort mit fb hinzutweaken. tschüss ;)

:rolleyes:

Dann kannste auch Pixelpost nehmen, auch multilanguage, alles das Gleiche, EXIF, RSS, ATOM usw. Größe kommt auch aufs Gleiche raus. 157kB gegen 13 kB Folderblog. Das ist es was mich reizt.

Tschüß!

meinst du man merkt einen geschwindigkeits-unterschied? denke fb verursacht die gleiche arbeit, schließlich wird bei fb ja auch nach jedem <#string#> gesucht. und das nicht zu knapp. is pixelpost ohne auch datenbank?

auch <-> ohne ;)

The inclusion of different language is definitely a minor problem. All that would be necessary is a line in fb.php like

if (fileexists(languagefile)) include(languagefile);

plus a little remodeling of the text strings in the same file. Thats all.

Generally speaking, if I understood you guys right you want to use fb 2 as the base for further development? I will definitely keep on developing my release based on version 3 as it has many major improvements.

>> if I understood you guys right you want to use fb 2 as the base for further development?

Definitly not. I will work with fb 3, thats for shure. As I understand Erik right, he would like to switch to other photo gallery software... hm. I will stay with folderblog.

And using language files is even possible without modifiying the fb.php. The local-variable is already set in fb_settings.php (used for LC_TIME) and I've just started to write a de_DE.po for my theme. Using the gettext()-function this is no big deal.

Well I never cared about anybody coming or leaving, I need to extend fb for own purposes and experience a certain level of joy from it. ;) You will understand me if you look into the fb source code... trying to modify something in there is sometimes like finding a needle in a heap of hay. Makes it more interesting, isnt it? ;)

So what were you guys saying about pixelpost back there in German?

"meinst du man merkt einen geschwindigkeits-unterschied? denke fb verursacht die gleiche arbeit, schließlich wird bei fb ja auch nach jedem <#string#> gesucht. und das nicht zu knapp. is pixelpost ohne auch datenbank?
posted by erik on 9 Jan 06 at 5:17 PM"

I've tested Pixelpost on my server and there was no difference in speed. Pixelpost is using a MySQL-Database which is the better solution if you got plenty of images, I guess.

This all depends on how you finally realize the internal functions... of course, if you need to read out e.g. EXIF information for sorting of the images, it is faster to read it out once, store it in MySQL and work in the future with that information. Reading out all EXIF data every time you visit the website takes more time, but also implies far less problems with things like updating and broken links.

However, nothing you guys should really care about as long as you dont put 5000 files into your photos directory and have a slow server.

I don't use exif data anyway.

Hi again Ikue :) I'm back. My client had a strange problem with his Folderblog installation. It currently has 160 images and is up to page 7. But if he uploads one more image then page 7 suddenly becomes blank. This happens if I upload an image too, so I know it's not the client being stupid.

Anyone have any ideas?