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 admin/content screen has a section that lets you do bulk operations on nodes. But it has no explanation/description of the process, and I don't think it would be obvious to someone who hadn't already had experience using it in Drupal 6 or been tutored on it.
See screen shot.
I suggest either adding a description text to the UPDATE OPTIONS field, or renaming it, or both.
My suggestion would be to change the field to say
BULK OPERATIONS
And to add a short description below saying something like
Select the content items to operate on from the list below, select the operation to apply to those items, and click "Update" to perform the operation.
| Comment | File | Size | Author |
|---|---|---|---|
| #19 | 677544syntax.patch | 4.61 KB | jhodgdon |
| #17 | 677544consistency.patch | 4.64 KB | jhodgdon |
| #16 | people.png | 13.11 KB | jhodgdon |
| #13 | 677544fixtests.patch | 1.62 KB | jhodgdon |
| #5 | 677544.patch | 919 bytes | jhodgdon |
Comments
Comment #1
jhodgdonComment #2
yoroy CreditAttribution: yoroy commentedUpdate options isn't ideal. main flaw is it doesn't link with having to select items in the table below. 'Bulk operations' are more difficult words.
'With selected items' ?
The proposed description is a variant on the 'this is a form that you have to fill out then click the button' pattern we've been actively weeding out from the UI.
Comment #3
jhodgdontag was removed, hopefully by mistake, by yoroy. Putting it back.
Comment #4
jhodgdonProposal:
Change the button text to "Update selected content" to explain what will happen if you click the button.
Change the label on the select list to "Choose action".
Comment #5
jhodgdonHere's a patch and a screen shot showing what it looks like.
Comment #6
jhodgdonComment #9
jhodgdonReported failures were in Tracker module tests. Unlikely to be caused by this patch.
Comment #11
jhodgdonHmmm. Same failure. I will investigate.
Comment #12
jhodgdonReal failure. I need to patch the Tracker test too. Coming soon...
Comment #13
jhodgdonThis patch fixes the tests as well as the content screen. If someone could review the changes...
Comment #14
Bojhan CreditAttribution: Bojhan commentedThis patch will need to be applied to other places as well, say for example People
Comment #15
jhodgdonOK.
Comment #16
jhodgdonWell, this is interesting. When I look at the People page, the options there are things like "Unblock the selected users". On the Content page, the options there are "Publish" (not "Publish the selected content"). See screen shot of people page.
So the People page is actually quite clear as it is, I think. So maybe a better fix for the Content page would be to ad "the selected content" to each of the options, rather than changing the button?
The Comments page is another spot (admin/content/comment), and that one is like People too.
I did a search for "Update options", and those three spots were all that came up.
So I think I'll fix node module so it has more verbose option names, and then I think we'll be consistent, clear, and happy. :)
Comment #17
jhodgdonHere's a patch. I also put the same items into the hook API documentation for the hook_node_operations hook.
Comment #19
jhodgdonHere's a patch that should, as an added bonus, actually work. :)
Comment #22
jhodgdonThis test passed with the patch applied on my system...
Comment #23
cweagansPatch applies with fuzz for me. Probably not an issue, though.
Everything works, and I like the changes to the strings.
Comment #24
jhodgdonprobably should wait for the retest to complete
Comment #25
jhodgdonAll of the locale tests definitely passed on my machine with this patch (that is what failed the last time).
Comment #26
cweagansUm? Looks alright to me?
Comment #27
jhodgdonMust have been a test glitch. Should be OK to go now!
Comment #28
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks!