[development] Best practices: Config settings
Tao Starbow
starbow at citris-uc.org
Thu Jan 3 21:23:37 UTC 2008
I agree that the best answer is both places. There is no reason to get
caught in either/or thinking.
I also I think this is the right answer to Khalid's issue about per-node
type settings as well. Sometimes you want to deal with all the settings
a particular node type has, but other times you want to just change one
setting for all the node types at once.
-tao
Bevan Rudge wrote:
> As a usability advocate I would push more for form_alter()-ing core
> forms when appropriate (like your example). As this makes logical
> sense. However, considering that most users who care about this
> variable are probably advanced drupal users, they will look for it
> first at admin/settings/YOURMODULE.
>
>
>> If you want, what you could do as a workaround is place a
>> drupal_set_message() (or hook_help()) on other pages that could be
>> affected by your setting that point back to the settings page. For example:
>>
>
> I think a better compromise is to put the form item ON BOTH forms.
> AFAIK there is nothing wrong with this technically, but I'm not sure.
>
> Bevan/
>
>
More information about the development
mailing list