Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The checkboxes should be used to remove the strings. Maybe replace them with X graphics ("remove"), apply some AJAX and have it use JavaScript to hide the item? Might be overkill, but hey!
Comment | File | Size | Author |
---|---|---|---|
#7 | stringoverrides_checkbox_usability_4.patch | 5.96 KB | RobLoach |
#6 | stringoverrides_checkbox_usability_3.patch | 5.44 KB | RobLoach |
#5 | stringoverrides_checkbox_usability_2.patch | 4.75 KB | RobLoach |
#3 | stringoverrides_checkbox_usability.patch | 4.26 KB | RobLoach |
Comments
Comment #1
zilla CreditAttribution: zilla commentedwhy would you need a checkbox? couldn't you simply copy what's on the left into the box on the right and then save - then you'll have an inventory of things you have changedthat you may want to change again...
Comment #2
RobLoachI was talking with John (clouseau), and he suggested adding a "Remove disabled" button at the bottom of the page that would remove the strings that are un-checked. Hitting the Save button wouldn't remove any items, it would just "disable" the string items that arn't checked.
This means that although we can keep the enabled strings in "locale_custom_strings_en", we'll have to hold the disabled strings somewhere else. Maybe "locale_custom_disabled_strings_en"?
Comment #3
RobLoachWith this patch, users can disable strings without removing them. There's an addition button at the bottom to "Remove disabled" strings. Testing appreciated.
Comment #4
jvandyk CreditAttribution: jvandyk commentedWhile this is an improvement, I think the checkbox column needs to be labeled "Enabled" so the user knows what the meaning of that column is.
Also, the form should be generated with a test for whether there are any existing strings. If there are no existing strings, the checkbox column and the Remove disabled button could be suppressed. Sadly, "Remove disabled" is not very clear either. Does it mean that clicking the button will disable the Remove feature? Or remove the disabled...what? Maybe "Remove disabled strings" would be clearer.
Likewise, the "More strings" button is unclear. Am I going to get some random strings that Drupal will generate for me? How about "Add row" instead, since that's what it actually does?
Comment #5
RobLoachHi John! Thanks for checking this out. I made some of those changes, but really have to go. So, this is a work in progress.
Comment #6
RobLoachThis is looking good now....
I'm not sure I like how "Enabled" looks in the table header row. It pushes the text fields to the right and makes it look like the columns are misaligned. I also like having the ability to select all the rows at the same time. Letting the user know what the checkboxes are for is important though, and I'm no usability expert, so I think it's your call, John.
Any thoughts? A search for
theme('table_select_header_cell')
will allow you to play with the Enabled column.Comment #7
RobLoachThere we go. Centering the column makes it look a bit better.
Comment #8
RobLoachDecided to commit this as it really improves usability. Thanks a lot for the ideas, John! http://drupal.org/cvs?commit=115775
If anyone wants to backport it to the Drupal 5 branch, please feel free to hit up a patch.
If 6.x-1.x-dev looks okay with you, John, I'd like to push a 1.7 release with this feature.
Comment #9
jvandyk CreditAttribution: jvandyk commentedRob, 6.x-1.x-dev does not seem to be saving my strings. I installed the module, entered some strings, clicked the add row button, entered another string, and clicked Save configuration, but although the message tells me "Your changes have been saved", they have not been saved.
Comment #10
RobLoachWhat browser are you using? Are you on a PHP 5 server?
Comment #11
jvandyk CreditAttribution: jvandyk commentedSafari 3.1.1. Yes.
Comment #12
RobLoachHmmm, very strange. I'll have a look to see what we took out that could be negatively effecting the forms.
Comment #13
RobLoachI can't replicate what you're experiencing in either Firefox/Gecko on Ubuntu Hardy, or Internet Explorer 7 on Windows.
Comment #14
RobLoachI'm pushing my luck with the 1.7 release, as it includes this patch.
Comment #15
jvandyk CreditAttribution: jvandyk commentedUsing Safari 3.1.2 I am not able to replicate the problem I was having earlier. So,cool!
Comment #16
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.