-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change some settings to properly reflect Enable/Disable Correctly #962
Comments
What's the UI best practice here? I feel a checkbox is pretty easy to understand... but radios, makes sense too. |
I think if it's a checkbox it needs to ALWAYS be "Enable". To check it in order to "Disable" is counterintuitive. But I think the radio buttons make it all as obvious as possible and avoid any confusion because they show ALL the options directly. |
I agree with @mathetos. Although check-boxes are simple operators, the current wording "Enable this option if you would like to disable the ..." can be very confusing. With radio button we remove the confusion factor from the equation. |
OK, here's a list of all the options on the "Donations > Settings" page tabs that need updating: Payment Gateways Tab
Display Options Tab
Emails Tab
Advanced Tab
Add-onsI'll make additional issues in the respective Addons that reference this issue, but from a quick review this would apply most often to the Payment Gateways. |
* release/1.7: (158 commits) Merge 1.6.1 into 1.7 Update filter give_payment_gateways --> give_donation_gateways Move payment-->donation in actions and filters Update general translation POT file update languages redame Delete PO/MO language files (Give) Delete PO/MO language files (CMB2) minor composer file update Readme: use https links Revert "Resolves #962" Resolves #962 Revert "Regarding #962 -- updates to Payment Gateways Tab" Revert "Regarding #962 -- updates to Display Options Tab" Revert "Regarding #962 -- updates to Email Options Tab" Revert "Regarding #962 -- updates to Advanced Options Tab" Revert "Use `show_option_none` instead of no value for CMB2 compatibility" Revert "Final cleanup of settings." Final cleanup of settings. Use `show_option_none` instead of no value for CMB2 compatibility Regarding #962 -- updates to Advanced Options Tab ... # Conflicts: # includes/admin/class-give-settings.php
* release/1.7: (29 commits) Merge 1.6.1 into 1.7 Update filter give_payment_gateways --> give_donation_gateways Move payment-->donation in actions and filters Update general translation POT file update languages redame Delete PO/MO language files (Give) Delete PO/MO language files (CMB2) minor composer file update Readme: use https links Revert "Resolves #962" Resolves #962 Revert "Regarding #962 -- updates to Payment Gateways Tab" Revert "Regarding #962 -- updates to Display Options Tab" Revert "Regarding #962 -- updates to Email Options Tab" Revert "Regarding #962 -- updates to Advanced Options Tab" Revert "Use `show_option_none` instead of no value for CMB2 compatibility" Revert "Final cleanup of settings." Final cleanup of settings. Use `show_option_none` instead of no value for CMB2 compatibility Regarding #962 -- updates to Advanced Options Tab ...
This is complete in |
Throughout the plugin we often mixed the purposes of settings between Enable/Disable, or Show/Hide in ways that can cause confusion.
Here's one example:
Three different settings, checking one enables, while checking another disables.
I propose something like the following instead:
This would apply to every setting that uses language like True/False or On/Off, Show/Hide, Enable/Disable. Consistency in our settings is important to the user experience.
The text was updated successfully, but these errors were encountered: