ok i kinda sorta felt like doing this because i had nothing else to do... but let me warn it's like highly alpha version, no admin setup yet (adding everything by hand in mysql so far) and it probably breaks alot of features :) but it works!!!
it allows for up to 5 levels right now (will be dynamic when i'm done) but does require at least one "album" level, so you can't just load pictures up into it you have to have at least one level of organization.
you can mix and match album and collection levels. like so:
main collection
/
\
collection
album
|
|
album
Pictures
|
pictures
so you can have collections with albums that mix and match sub-albums or albums with pictures.
collections cannot contain both a sub-album and pictures, i thought about it... but it's too little gain for the effort.
I'm sure you can see i'm not using a common terminology... it's basically like this:
collections hold other collections and albums albums only hold pictures
well check it out and let me know if it's in the right direction and weather or not you see any bugs/weirdness
i do already know the count for albums/pictures is off cause i'm not done there yet and the jump-to menu is just missing... and the search probably doesn't work too well.
ok, it's been a while.. a pretty long road, but i have an alpha version ready, it's rough and only the basics really work correctly..
here's the skinny found in README-MULTI.txt included in the main directory of the distribution:
Alot has been changed in this multi-level, multi-program integrated version of plogger.
up to 5 levels of organization can be created or as little as one. (working on the no level just pictures)
File uploads work for ZIP files, haven't tested individual pictures, import works on uploads directory, Approval page should work if you want anonymous uploads to be enabled (turn on/off through options tab).
Under the manage you can add/delete collections/albums editing is still sloppy but may work...
DO NOT USE THE "Move Album" or "Move Collection" They do not work and can cause serious injury to your database.
Everything else may or may not work, use at your own risk!!!
I Highly doubt you should use this for a production use, this is more of a proof of concept ALPHA build, though you could.
INSTALLATION:
run the _install.php and create everything as a normal plogger install.
then run _multi.php which will modify the database so that everything is setup correctly for this version.
that should do it, upload pictures, create collections/albums as you wish.
CONVERTING from PLOGGER Beta 3 to PLOGGER-MULTI Alpha 1
no conversion scripts have been made, i can help you if you would like to do this on the plogger forums but it is not recommended
OK now that you've read the warning i'm putting up the disclaimer that i'm not responsible if you install this version and something happens... USE AT YOUR OWN RISK
ok all that out of the way i'm calling this version plogger-mult and you can download it HERE
Well, I always like it when people go and try out all kinds of modifications to suit other needs, so I like what you're doing. I'm not sure though if I will use it myself because I like the two-level organisation. It keeps things simple and you don't have to click your way through many many levels. But I can see that in some cases it could be very usefull. I myself now have collections > albums like this: animals > cows and cats > mickey and cats > behind windows. But cats are animals... , so that's an inconsistency in the organisation. I don't really care much, but one extra level ... ;). But then again, I like it the way it is, I only could use an option to assign one image to multiple categories, but that's something else.
Anyway, nice work. I'm curious to what other people think about it.
sidtheduck created a Trac ticket to further discuss the possibility of including this in the Plogger core: http://dev.plogger.org/ticket/184. Currently, the milestone for this is version 2.0.
You might check out what's already been discussed over there, and contact sidtheduck about possibly working with him to begin implementing this within the current codebase.