The fact that drupal does not use the chosen theme on the blocks page is an improvement. Now the admin theme controls the look of this page and keeps you from naughty surprises and funny styling issues due to a themer having not looked how the blocks page looks.

But alas, it comes at a cost - now you have an even harder time to instantly realize for which theme you are setting the blocks.
A very simple and effective means could solve that: Just put a small version of the chosen theme's screenshot in the upper right corner next to the tabs that choose the theme for which you edit the blocks. Simple, effective, hardly any effort.

Files: 
CommentFileSizeAuthor
#16 blocks-themes-before.png82.18 KBeigentor
#16 blocks-themes-after.png84.03 KBeigentor
#16 blocks-themes-after-title.jpg96.52 KBeigentor
#15 block-admin-primary-tabs-735692-15.patch1.25 KBJohnAlbin
PASSED: [[SimpleTest]]: [MySQL] 24,806 pass(es).
[ View ]
#13 block-admin-primary-tabs-735692-13.patch6.58 KBJohnAlbin
FAILED: [[SimpleTest]]: [MySQL] 24,811 pass(es), 0 fail(s), and 50 exception(es).
[ View ]
#12 block-admin-primary-tabs-735692-12.patch3.5 KBJohnAlbin
PASSED: [[SimpleTest]]: [MySQL] 24,799 pass(es).
[ View ]
#9 block-admin-with-primary-tabs.png77.68 KBJohnAlbin
#9 block-admin-primary-tabs-735692-9.patch1.36 KBJohnAlbin
FAILED: [[SimpleTest]]: [MySQL] 24,825 pass(es), 2 fail(s), and 0 exception(es).
[ View ]
blocks-page-theme-screenshot-2.jpg44.71 KBeigentor

Comments

It also strikes me that jumping to the blocks page defaults in opening block editing for Seven theme. While this may make sense as it opens the theme that is active in the screen you look at, in much more than 80% the user will want to edit the blocks for the default front end theme. So this should default to the default theme. This reduces the error this issue strives to solve for most users, and the screenshot should kill it for the rest.

Initially showing the blocks for the default front end theme is a much bigger win. I know I have been spent minutes wondering where my sidebar regions went only to find out I was looking at blocks layout for Seven instead of Garland. Repeatedly.

I'd much prefer to work on the show-default-theme block settings that than adding the screenshot.

I agree the default setting is more important. Stborchert also does not like the screenshot :P. Still we need something more than the teeny tiny tab to indicate what's the Theme we ard setting the blocks for.

Title:Add theme screenshot to blocks pageBlocks admin page does not show clearly which themes blocks are edited

Changed title to better reflect the issue

Also @Add new block@ is lost

Can we perhaps change the title of the page? Ie Blocks of Seven?

@Bojhan Good idea and it's easy to implement

StatusFileSize
new1.36 KB
FAILED: [[SimpleTest]]: [MySQL] 24,825 pass(es), 2 fail(s), and 0 exception(es).
[ View ]
new77.68 KB

So, I was noticing this oddity about the block admin page yesterday. It has no primary tabs. In D6, the tabs were "list" and "add block", but "add block" was rightly converted into a local action link, leaving "list" as the sole and pointless tab. (Plus if there is only one primary tab, it gets hidden by default.)

Why not convert the block admin's secondary tabs into primary tabs?

Here's a screenshot and a patch.

Status:Active» Needs review

Review, of course!

Status:Needs review» Needs work

The last submitted patch, block-admin-primary-tabs-735692-9.patch, failed testing.

Status:Needs work» Needs review
StatusFileSize
new3.5 KB
PASSED: [[SimpleTest]]: [MySQL] 24,799 pass(es).
[ View ]

Fixed the block tests.

StatusFileSize
new6.58 KB
FAILED: [[SimpleTest]]: [MySQL] 24,811 pass(es), 0 fail(s), and 50 exception(es).
[ View ]

Fixed the help text so it displays on all tabs. Fixed the links to the demo pages. And fixed a link from the dashboard to the block admin.

Status:Needs review» Needs work

The last submitted patch, block-admin-primary-tabs-735692-13.patch, failed testing.

Status:Needs work» Needs review
StatusFileSize
new1.25 KB
PASSED: [[SimpleTest]]: [MySQL] 24,806 pass(es).
[ View ]

The patches above were pretty small, but I actually made them much more complex then they needed to be. I didn't need to remove the "list" part of the path, I just needed to remove the "list" primary tab; then the secondary tabs got an automatic promotion. The "list" part of the path are actually necessary so that you can have themes named "manage" or "demo" or "ADD" or any other path that a contrib module wanted to add underneath admin/structure/block.

Here's a much simpler patch that does the same thing. I ran some of the simpletests on my system, so I don't expect it to break any tests when the bot gets a hold of it.

StatusFileSize
new96.52 KB
new84.03 KB
new82.18 KB

This is looking much better. Cannot judge the code quality, just reviewing Design.
For direct comparison before and after:

Without Johns Patch:

Improved Version with Patch applied

This is how it looks with Bojhans idea to also write the theme name into the title:

Bit of a mixed bag, this last version. While it sure helps to know which themes blocks you are editing, the word "Blocks" is not as prominent as before, so it might take longer to scan that you are on the blocks page.

I just took a look at block_menu() and from a technical aspect, I don't think it is possible for tabs to affect the title of the loaded page. Maybe with a title callback on the parent path? :-\

Also, I personally think the primary tabs make it much more obvious which theme the blocks are being configured for; altering the title doesn't seem necessary.

Title:Blocks admin page does not show clearly which themes blocks are editedUnclear which themes blocks are edited - shown as secondary tabs without primary parents
Category:feature» bug
Status:Needs review» Reviewed & tested by the community

Nice catch JohnAlbin! This is essentially a UI bug and the fix looks good. Worth committing, this is much clearer. Adding the theme name to the page title would be additional polish, which I hear is not what we're supposed to be doing these days :-)

This is MUCH better. Yay!

I hope this is committed. I agree that the way it is now is very confusing and to be completely honest, the secondary tabs all by themselves just look like crap. I think that's what's so confusing about it. It's just not designed to be used that way.

Hmm, actually I think the weights need a little work. The breadcrumb trail is wrong.

Testing with Seven as default theme and the overlay disabled, I get the following:

path | breadcrumbs
admin/structure/block | Home » Administer » Structure
admin/structure/block/list/bartik | Home » Bartik » Blocks
admin/structure/block/list/garland | Home » Garland » Blocks

I guess this could also be an unrelated bug (maybe #907690: Breadcrumbs don't work for dynamic paths & local tasks #2), but I'm not sure. Any ideas?

Good idea. Can't reproduce what Jacine reported. Perhaps she didn't rebuild the menu after applying the patch (which just landed).

However, I'm getting other odd results, but which are only related to #550254: Menu links are sometimes not properly re-parented

Status:Reviewed & tested by the community» Fixed

Committed to CVS HEAD. Thanks.

Status:Fixed» Closed (fixed)
Issue tags:-Usability, -D7UX

Automatically closed -- issue fixed for 2 weeks with no activity.