RE: [PHP] This, then that.

On Sat, 2007-10-20 at 09:59 -0400, tedd wrote: > At 4:59 PM -0400 10/19/07, Robert Cummings wrote: > >On Fri, 2007-10-19 at 13:31 -0700, Instruct ICC wrote: > >> > I want to prohibit an image from being shown to anyone who is not > >> > permitted (i.e., logged in). > >> > > >> > The way I want to do this is to: > >> > > >> > 1. Set [file] permissions... > >> > >> > >> > >> What if 2 or more users access the application at the same time? > >> > >> Set the permissions so only the PHP application can access it. > >> Have the PHP application decide if this present user running this > >>instance should see the image. > >> If approved, display image. > > > >One idea that has always been REALLY popular around here... stuff your > >image in a database. *MUHAWHAWHAWHAWHAW* *Ducks from the flying rocks*. > > > >Cheers, > >Rob. > >-- > > Rob: > > That's really not a bad idea, but in this experiment I'm using images > as a stand-in for larger files (CD's, Videos, etc). > > Side note to everyone else (Rob knows this) Storing images in a dB > has some advantages, but the concept has been beat to death on this > list and no need to repeat it -- everything that could be said > pro/con has been said -- just review the archives. I use the db for images sometimes. I don't really care what some people think since I've thought it out for myself and like th epros versus the cons sometimes. At any rate, y our problem appears to be related to safe_mode for not putting images outside the web tree. Most likely though, you have access to .htaccess and so you could create a locked images directory that exists within the web tree but which can't be accessed by a browser. This would give you what you need to be within the confines of safe mode. Cheers, Rob. -- ........................................................... SwarmBuy.com - http://www.swarmbuy.com Leveraging the buying power of the masses! ...........................................................