Custom Fields again

[Joel Peshkin]

David Miller wrote:

> Why do it from the web?  Adding a custom field is either an initial
> configuration thing or it's a Big Deal to add when you do it.  Use a
> command-line utility in the shell to do it (just like checksetup.pl) or
> even use a data file (localconfig?) to declare what should be there, and
> have checksetup.pl do that when it runs.  Choosing which products it's
> valid for and what the multi-select values are for multi-select fields
> could certainly be done from the web interface however
>

Using localconfig solves several problems.  If I add a field using 
localconfig and run checksetup to get it into the DB, it clears up many 
migration issues that apply to fields added by sites using checksetup. 
Once a field is added using localconfig, then it should be possible for 
me to use the web interface to specify how that field is processed and 
displayed OR I should be able to use the web interface to specify how 
that field is processed and customize templates myself to handle the 
display activity.  This gets us the best of both worlds.  Someone who 
only touches localconfig and the web can use custom fields.  People who 
customize templates can get a bit more mileage out of it.