I see the build_images_url was added :)

Also, in looking at the code, wouldn't it be easy to have the admin generate the "config" screens from a database table, and create the config-hash from that??

Rather than coding the description and details in the HTML, create an input form, that edits the variables that are kept in an SQL table, then writes them out to the ConfigData.pm file on exit/save.

Each item would contain, just eyballing it:

Key,
Value,
Description (text)


Also, this could be linked to the help system, by adding a field for "help".

Then, the admin screen would just be generated from the same template parser the rest of the program uses.

Multi-page configuration options could be stored to separate tables, or have the fields prefixed with page1_ page2_ etc...

Make sense?

That would allow users to enter configuration variables from the admin, they are kept in the config table, and written out to the "include" config file.

Everything works the same way, nothing hard coded, and any new variables/settings are automatically updated when changed....

http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/