[dev] Re: Web-based administration of prefs.php values

[Kevin Myer]

Then the proper place to implement this would be in the Setup portion for
Administrators?  I'm thinking you could add one or two columns.  You have the
existing application name in one, and the status for that (which lets you know
if something requires a change after an update.  Then you'd have a preferences
column with a link to change preferences for the application, and a 
preferences
status that functions similarly to the configuration status - if something is
added, or changed that requires a regeneration of prefs.php, it would be
flagged there.  Or you combine the two - just have a preference column that is
a link to change preferences or gets a checkbox and it states 
"Preferences need
updated" if a change is required.  And take that one step further, use the
Setup screen to generate your registry.php.

So something like this:
"Application"   "Configuration Status"  "Preference Status"
A               B                       C

Where A lets you enable/disable modules, and specify registry related items
(like your webroot), B is either a link to do configuration and it 
changes to a
notification, with a link, if Configuration needs updating, and C is the same
as B, except for Preferences.

I'd think a lot of the code to do this would already be written (at least the
generation of the preferences widgets) and it would be a matter of modifying
this to allow entry of additional or new values.  If one of the preferences
depended on a value provided by another application (like IMP's
autoexpand/Expand Name functionality depending on sources/preferences defined
in Turba), have the values pulled from those application preferences, and
enforce a default order of setting up preferences (i.e. first Horde, then
Turba, then IMP, etc.)

Just thinking aloud here - concept only at this point :)

Kevin
-- 
Kevin M. Myer
Senior Systems Administrator
Lancaster-Lebanon Intermediate Unit 13  http://www.iu13.org
(717) 560-6140