Hi all, my boss’s son wants me to build him a photography portfolio site - I can do this relatively easily. However, he wants me to build a client login section on the site, now not sure of the best way to implement this.
How would you guys to do?
I’ve had a couple of ideas:
(1) To create a folder on the server for the images when a client-login username/password has been created and then let him just drop all of the images on the folder and use scandir or something.
(2) To have upload boxes for each image and then enter the name into the database as well as uploading the file.
(3) I think it will be best for him to create thumbnails of each image and upload them to.
Hey dude, it will be for clients of his that he show images to of their images of that makes sense. For example if I wanted some portraits of myself, I would go to him, he’d shoot them and send me a username/password so I can view the images he taken and decide which I do/dont like.
ok, I would make a mini CMS for him. He would need to make user names, generate a pw, say these photos go with this day/session/event, allow the people tell him selections etc,
Thanks for your message. So how would you go about uploading the images, would you give him the option to upload each file, though if he has say 50 images, that would be quite time consuming.
The other idea I had would be to generate a folder when he creates the username and password and then just drops in all the images in that folder and display then all using scandir or something?
You would probably need a batch uploader, then the next screen would be put these pics in session. You could create a directory based on user/event. all the organizing will be in a database. So your database would have tables for: users, photos, which photos the user liked. If you have time, I would insatll gallery, see how it is set up. You won’t need all of its features so get ideas how to organize.
I wouldn’t bother with a username and password. Instead when he adds a job, or shoot I’d generate a random 12 character code that is unique to each shoot, then email a link with that in the query string to verify access. It’d be quicker, for photographer and the user (they don’t have to type username/password, just follow the link in the email), and the data being protected isn’t highly sensitive. It’s enough to stop casual browsing from people without the link.
Uploading a batch of photos by FTP or, zipping uploading the zip, and having the server extract the zip would probably be the way to go. Either that or implement some Flash based multi file uploader. The photographer should batch resize their images before uploading. Even though the server could do this, the upload will be much faster if he’s not uploading 300 megapixel goliaths.
Hey dude, thanks for your message, I think that’s probably the best way to go. I just couldn’t work out how implement this in a way which works well and is non-taxing for the photographer. Thanks all for your help as always
