Well my sister had a child, and wanted to share pictures with everyone, so of course i set her up an install to share her new boy with family and friends...and while she definitely liked it, her first question was, how can i move all this around? I had catagorized it for her. Now it must be stated, she has no interest in the ease of ftp, nor a need to use it elsewhere. I quickly realized what had to come next...
This release includes a set of pages allowing the admin user to Create and Rename Folders as well as Upload and Move images from folder to folder.
Any time images or folders are moved or renamed, any data saved about those images moves with them.
I did away with the 'Admin' cookie concept, this seemed a week link in security, as its not hard figure out how to set your own cookie and possibly gain access to anothers machine also running theimages. All administration pages have been moved behind a login with session-based authentication. Also, both username and password are encrypted when saved to the server, so no plain text is available. The next step will be to add it to mysql, but for now, i'm trying to make this as useful as i can with/without a db, so many things will get done as files first. I'm considering a flat file CM system as well...
For Updraders ...
There was one minor change to config.inc.php, so please check the change log. I'd suggest saving your current file before installing and replacing it back. Then make the chanes to the IMAGE_DIR define as noted in ChangeLog/INSTALL You'll need to before you use the admin pages to maniputlate foders and images. I hope its working out for you.
Please post this list, send a bug report or feature request if you have them, or just email me. I'd be happy to encorporate peoples ideas.
Reports for image stats are coming soon, most likely this week.
Then possibly...
End user security so the admin can only allow certian people access to certian areas,
Or to separate the GUI from the code better allowing for more of a customized look. Possibly migrating to a class structure. A rewrite that would be brougt up in parralell to this code.
Maybe a Port to Perl?
Jeff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well my sister had a child, and wanted to share pictures with everyone, so of course i set her up an install to share her new boy with family and friends...and while she definitely liked it, her first question was, how can i move all this around? I had catagorized it for her. Now it must be stated, she has no interest in the ease of ftp, nor a need to use it elsewhere. I quickly realized what had to come next...
This release includes a set of pages allowing the admin user to Create and Rename Folders as well as Upload and Move images from folder to folder.
Any time images or folders are moved or renamed, any data saved about those images moves with them.
I did away with the 'Admin' cookie concept, this seemed a week link in security, as its not hard figure out how to set your own cookie and possibly gain access to anothers machine also running theimages. All administration pages have been moved behind a login with session-based authentication. Also, both username and password are encrypted when saved to the server, so no plain text is available. The next step will be to add it to mysql, but for now, i'm trying to make this as useful as i can with/without a db, so many things will get done as files first. I'm considering a flat file CM system as well...
For Updraders ...
There was one minor change to config.inc.php, so please check the change log. I'd suggest saving your current file before installing and replacing it back. Then make the chanes to the IMAGE_DIR define as noted in ChangeLog/INSTALL You'll need to before you use the admin pages to maniputlate foders and images. I hope its working out for you.
Please post this list, send a bug report or feature request if you have them, or just email me. I'd be happy to encorporate peoples ideas.
Reports for image stats are coming soon, most likely this week.
Then possibly...
End user security so the admin can only allow certian people access to certian areas,
Or to separate the GUI from the code better allowing for more of a customized look. Possibly migrating to a class structure. A rewrite that would be brougt up in parralell to this code.
Maybe a Port to Perl?
Jeff