Posted by bigjim on February 1, 2012 at 5:37pm
3 followers
Jump to:
| Project: | Views Bulk Operations (VBO) |
| Version: | 7.x-3.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
Single On/Off fields (ie Boolean) are not displaying both options to the user performing the bulk update. Only the "On" value is displayed, while the "Off" Value is insinuated by not checking the box, which is not clear from a UI/UX perspective. This is a change from the way it worked in D6 where both the on and off options would be rendered in a drop down Select.
Comments
#1
That's how Drupal core handles booleans. Go to a node add or edit form and you will see a checkbox for "Published", for example.
So we are following that for consistency. I actually find the D6 way odd.
So this won't be changing unless I see big pushback.
#2
Updating individual nodes (or entities) one by one is a different use case than updating them en masse from a UI perspective. Especially with Single On/Off Fields where the Off option isn't always just "no" but may have a more verbose label that is significant to the users.
personally I know this is making our users nuts and making training a little more difficult
#3
Okay, let's get a few more opinions.
Basically, if a value is selected for updating, not being selected (Off) always means no. That needs to be communicated to users.
#4
Are we saying we sghould display a message is there is a boolean field? or changing the element of the field?
#5
I clarified to Damian what the issue here is (checkbox VS select box). He agreed that we shouldn't reinvent the look of the boolean field.
#6
Roger that!