Tao-<br><br>Is this double positioning an acceptable solution from a general usability standpoint? <br><br>If so, I'm all for it and we should make it standard practice.<br><br>- Ken<br><br><br><div class="gmail_quote">
On Jan 3, 2008 4:23 PM, Tao Starbow <<a href="mailto:starbow@citris-uc.org">starbow@citris-uc.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I agree that the best answer is both places. There is no reason to get<br>caught in either/or thinking.<br><br>I also I think this is the right answer to Khalid's issue about per-node<br>type settings as well. Sometimes you want to deal with all the settings
<br>a particular node type has, but other times you want to just change one<br>setting for all the node types at once.<br><font color="#888888"><br>-tao<br></font><div><div></div><div class="Wj3C7c"><br>Bevan Rudge wrote:
<br>> As a usability advocate I would push more for form_alter()-ing core<br>> forms when appropriate (like your example). As this makes logical<br>> sense. However, considering that most users who care about this
<br>> variable are probably advanced drupal users, they will look for it<br>> first at admin/settings/YOURMODULE.<br>><br>><br>>> If you want, what you could do as a workaround is place a<br>>> drupal_set_message() (or hook_help()) on other pages that could be
<br>>> affected by your setting that point back to the settings page. For example:<br>>><br>><br>> I think a better compromise is to put the form item ON BOTH forms.<br>> AFAIK there is nothing wrong with this technically, but I'm not sure.
<br>><br>> Bevan/<br>><br>><br></div></div></blockquote></div><br>