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.
Problem/Motivation
Since the hook_help text for the Blocks module was written, its Administration page has been changed. The "Place Blocks list" has been removed, and replaced by a button per region, but the help text was not updated.
Proposed resolution
Update the hook_help text.
Check the UI text on the Blocks administration page and update it if necessary as well.
Remaining tasks
Update the hook_help text, and possibly the UI text as well
User interface changes
This is a UI text change.
API changes
None.
Data model changes
None.
Beta phase evaluation
Issue category | Bug because the User interface was changed, but the help text was not changed accordingly |
---|---|
Issue priority | Minor |
Unfrozen changes | Unfrozen because it only changes strings in the hook_help for the block module |
Disruption | None |
Comment | File | Size | Author |
---|---|---|---|
#17 | 2572513-14.patch | 2.84 KB | MattA |
#17 | 2572513-13-14-interdiff.txt | 1.52 KB | MattA |
Comments
Comment #2
marjadoedens CreditAttribution: marjadoedens commentedI'll be working on this today.
Comment #3
marjadoedens CreditAttribution: marjadoedens at Wowww commentedI updated the help-text of the first use because the interface was changed.
Comment #4
pguillard CreditAttribution: pguillard commentedAccording to me, this is RTBC
Comment #5
ifrikThanks a lot, and congratulations for making your first patch!
I've added the beta-evaluation, so it just needs waiting for the test to finish.
Comment #6
yoroy CreditAttribution: yoroy at Wunder commentedThis change is good. If changing the UI text on top of /admin/structure/block is also in scope of this issue then we still have work, because there it still refers to the right sidebar that is now removed.
Comment #7
ifrik... that should teach me to read my own issue descriptions properly in future....
I'm adding that to the patch now, because as far a as I know the mdoedens is not around during the extended sprint.
Comment #8
ifrikIn fact the UI text on that page had quite a few errors in it by now.
I've restricted the text to issues: that you need to place the blocks per theme, and that you need to click save at the bottom, because these are not obvious when you look at the table.
There isn't much explanation that could be added for the "place blocks" or "configure" links that users wouldn't see when they click on either link, so I would rather not clutter up the explanation text with any of that.
Comment #9
MattA CreditAttribution: MattA commented1a.
Hmm, technically the tabs at the top of the page already imply that these are per-theme settings. If that is clear to users, the part explaining how themes implement regions kind of becomes irrelevant too. So I wonder if the first sentence could be removed (or just emphasize the per-theme-ness)?
1b.
Of course if that sentence gets removed, the phasing of the next one becomes a little weird. A quick fix would be to just use what it was supposed to be from the patch/botched review that created this issue:
After moving blocks, remember that your changes will not be saved until you click the <em>Save blocks</em> button at the bottom of the page.
2.
Not relevant to this issue, but thought I'd take the time to remind people that this is a regression (which should be fixed by #2514150: Advertise the block region demonstration in a more prominent way).
Comment #10
ifrikThere is nothing on the page that alerts users that the blocks need to be set per region - the tabs only give the names of the enabled themes, and the place blocks pop-up does not have any information about in which theme you are placing the block at all.
So the chance of users missing the fact that blocks are placed per region are really high. Therefore we really need to keep that information.
The reminder to save changes is there because even though there is a message displayed at the top of the page, a user can miss the save button as well as the message when they move a block somewhere in the middle of the page.
Comment #11
MattA CreditAttribution: MattA commentedI really wouldn't say that this page has nothing on it informing users about what is going on. Obviously, having the UI heavily imply something isn't as great as making it explicit to the user (like this), but eventually we have to give them some credit. At the end of the day though, we'd really need a usability test to determine the probability of them misunderstanding the concepts on the page and if help information could even fix it.
Also, I never said anything about removing the save button sentence. Only that it's phasing would be off if 1a happened. That thing is so far off the screen, it might as well be in Antarctica...
Comment #12
jhodgdonIn the latest patch:
You need to place the blocks specifically for each theme because not all themes implement or display the same regions in the same way.
This seems unnecessarily verbose... if (given the above discussion) we do need to say something about this, how about if we just change it to say something like:
Block placement is specific to each theme on your site.
Comment #13
ifrikThanks, having that sentence shorter is a good option.
Comment #14
jhodgdonI think that the patch is very sensible. It removes the part of the page-specific help that was telling how to use the UI, which is something we are not supposed to do, and leaves in a concise 2 sentences for 2 things you might not notice. Tenatively RTBC...
Comment #15
MattA CreditAttribution: MattA commentedSatisfies both 1a and 1b of #9, so +1 RTBC pending testbot results.
Comment #16
yoroy CreditAttribution: yoroy at Wunder commentedThis is looking good. I have one nitpick:
sounds a bit weird to me. Maybe this is a bit simpler:
Comment #17
MattA CreditAttribution: MattA commentedHmm, I guess that does sound a little weird. How about "the Region drop-down list" instead though. That is what is used in other parts of core like the help text for the Action, Editor, Field UI, and Language modules. Also, "drop-down" is technically a programmer-specific term for a UI element which normal people may not understand, so at least those people can clue in with "list".
Comment #18
MattA CreditAttribution: MattA commentedOops. Too early in the morning for me. Just did a previous patch number + 1 instead of looking at comment number there. Oh well...
Comment #19
yoroy CreditAttribution: yoroy at Wunder commentedYep, doesn't hurt to keep the 'list' keyword in there. Thanks!
Comment #20
jhodgdonIt seems that Yoroy likes this. I like it too. Let's do it.
Comment #21
xjmI tested manually and confirmed that this describes the new behavior.
This is much more readable now; nice work!
Committed and pushed to 8.0.x. Thanks!