Hi there, thanks for looking at our project!
We are an "auto classifieds" website, which uses a very simple, tab-delineated flatfile database for all the vehicle records.
A couple of years ago, we hired a programmer to make an "account features" script for the site. This script allows a user to log in, add / edit / or remove listings. The script is a CGI script and works with the flatfile database. The "add" module also allows for the upload of images, which are then processed (in a very simple way) by imagemagick. This all works just fine.
We need just a couple of minor mods to this script, as follows:
1.) Currently, the script is saving the photo filenames for each record in relative URL form (i.e., /photos/[login to view URL]). We need a minor modification so that it will save them in absolute URL form (i.e., [login to view URL]). The absolute URL domain will always be the same, so this is a VERY quick minor mod.
2.) Currently, the script is not resizing any photos that are uploaded. We would like for the script to be telling imagemagick to resize all photos to 640 pixels wide. (proportions should be constrained, i.e., please don't distort the image). This, I believe, is also a very simple mod.
3.) The third and last mod we need is a little more complicated to explain, but is actually simple when you understand it. When a new record is added by this script to the flatfile database, field 9 of each record is the unique "record ID", and fields 18-27 are the photo URLs.
Currently, the script creates a record ID for each new listing that is added (i.e., P1010449) and then names the photos accordingly (i.e., [login to view URL], [login to view URL], etc.). The change we need is this -- that field 9 "record ID" needs to be written differently. It needs to be generated by concatenating the content of field 12, an underscore, and the content of field 11. So, if field 12 contains "HDA", and field 11 contains "3053", then when creating that new record, field 9 should be written as "HDA_3053".
To clarify, it is not necessary to change what the script internally considers the "record ID" to be (in other words, what it uses as the basis for the photo filenames). It is only necessary to change what it writes into field 9. However, if it's easier for you to think of it in the opposite way, it's ok to change it so that new photo filenames are based on the new "name" in field 9.
Does that make sense? They are actually three pretty quick things, but if you're unclear about what we need, please don't hesitate to ask. We welcome your bids, but please have experience working with CGI and flatfile databases. (We're not interested in new turnkey systems, or MySQL solutions. This is just a few simple mods to an existing script.) Thanks!