Forum Moderators: coopster
I hope this helps.
I prefer to store the images in a directory and save their filenames in the SQL database. The database stays (much) smaller and the image files easier to check out and fiddle with.
Whether you keep the images in the database or in the file system, the images will probably be the trickiest part here. You might want to get the hang of SQL a little before you add handling images to the mix.
Timster: I didn't mean to suggest storing the images themselves in the database, but only the paths to them, alt text, etc.
Yuppster: I suppose that if you feel more comfortable writing and reading files than you do working with a database, you could come up with a format for storing the data in a flat file. If you're not trying to store too much, the simplest thing might be to serialize() [us2.php.net] your array(s) and write those to a file.
I hope this helps.
I was talking about a different way to store the data (descriptions and links to images) other than a database... like in an array or an external file somehow through php. I just don't think I'm technically up to messing with a database just yet. Thanks alot
If it were me, trying to make do with some text files heres what I might do:
-i would store all the info that you say you would get when you clicked on a link, in a single textfile, with the file name being the link itself. You can get the list of them from directory reading functions, or alternately make a separate file with urls in it, one per line.
-the format of a single file of one url would be something like the image path on the first line, and the rest of the file being description text. If you wanted to you could keep the image filename the same as a url and load it up simply like that (i.e. www.foo.com.jpg)
hth-