oop, hit "send" too quick. -1 on changing the name dynamically. Its very bad for useability to have form items change into other iotems based on changing settings. A form item should remain the same. Always. OR might dissapear, but certainly not change into another one. Op dinsdag 8 maart 2005 03:03, schreef Andre Molnar:
-1 for this change - UNLESS there is empirical data to suggest that the majority of Drupal installs do not use the default front page (i.e. they use something else).
"Promote to front page" is not confusing in any way. And if someone is advanced enough to change their front page, I think they would understand that "Promote to front page" means "Promote to the page that is normally the front page."
The real solution is to test what the default front page is (perhaps even create and store a new flag) and change the wording of the option box based on that.
Pseudo code:
If($default_front_page) { form_checkboxes(t('Promote to front page') /*MORE CODE*/); } else { form_checkboxes(t('Is Headline') /*MORE CODE*/); }
Long story short - The cons of the proposed change AS IS outweigh the pros.
andre
Bèr Kessels wrote:
Hello.
Currently we use the standard flag called "promote to frontpage". This is only correct for those cases where /node is the frontpage. For all other cases, thes flag is obsolete, if not completely wrong.
I suggest the folloiwing: We stop calling /node frontpage. We call /node "headlines", in documentation and help text. By default the headlines are set to frontpage (we have that now) We rename the flag " promote" to "add to healines", or even simply "is headline"
Pro This will improve useability for all these ppl that do not use /node as frontpage. It will make our frontpage system clearer, for /node (headlines) becomes just another frontpage option.
Con: Users who are used to the current system might get confused when they do not find the "promote to frontpage flag" anymore. Regards, Bèr Regards, Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]