[drupal-devel] forms should reflect settings.php hardcodes

[Kobus Myburgh]

I agree with Ber in principle, however, it should not disappear, but rather greyed out with a notice why it is greyed out, because people will think that Drupal don't support that specific setting. Optionally also import the content of the hardcoded text into the textarea/field before greying it out. That would clear up a lot of confusion in itself if they can see what the predefined content is.

Regards,

Kobus


>>> berdrupal at tiscali.be 9/27/2005 11:05 AM >>>
Yet another minor issue, that can lead to Mayr annoyances.
when a setting is set in settings.php, for example the site slogan, one can 
still set that slogan in admin/settings. 
That is strange, and very confusing. A 'hosting provider' such as BygHost, 
might choose to set harcoded footers 'supported by BygHost'. 
Users will be very confused why they changed theyr footer, yet the site does 
not change it.

The field of any setting that is harcoded should best dissapear, or otherwise 
be greyed out. 

Is that possible with the form API?

Ber