Updated: Comment #0
Problem/Motivation
In #2055853: [meta] Improve the place block UX; Separate interaction from the create block UX; Improve the existing blocks-by-theme layout it was determined that the current path structure was confusing.
Proposed resolution
Move the custom block pages below the block UI, instead of next to it
Remaining tasks
N/A
User interface changes
The custom block pages move, and the per-theme tabs are now secondary instead of primary
API changes
N/A
Related Issues
#2055853: [meta] Improve the place block UX; Separate interaction from the create block UX; Improve the existing blocks-by-theme layout
#1926294: Write tour integration for block_content.module
#2078635: Add an 'Add custom block type' local action to the 'Custom block library' Postponed on this
Comment | File | Size | Author |
---|---|---|---|
#17 | bl1.jpg | 160.68 KB | dcrocks |
#17 | bl2.jpg | 146.62 KB | dcrocks |
#9 | block-2078341-9.patch | 18.83 KB | tim.plunkett |
#9 | interdiff.txt | 769 bytes | tim.plunkett |
#4 | Screen Shot 2013-08-31 at 1.21.05 PM.png | 120.75 KB | tim.plunkett |
Comments
Comment #1
tim.plunkettFirst pass.
Comment #3
Bojhan CreditAttribution: Bojhan commentedDoes this mean it becomes a tab? How do you access this outside of the vertical menu?
Comment #4
tim.plunkettHere is the regular blocks page, now called "Block layout". The difference between 7 and 8 is that the theme-specific tabs are now secondary tabs.
Here is the custom blocks page, which has a default secondary tab for the custom blocks, and the other secondary tab is the custom block types:
Comment #5
tim.plunkettIf we do not make "Custom block library" a local task, then the only way to get there will be through the vertically expanded toolbar.
Every other instance of a page being a subpage of a listing is a local task. Think of the Comments page (admin/content/comments) under the Content page (admin/content) or the Views settings (admin/structure/views/settings) under the Views listing (admin/structure/views).
Unless we choose to just keep the page title changes and nix the entire restructuring, we're pretty much forced to use local tasks like this (and for the record, I think this is an improvement).
Comment #7
larowlanI could support this if we also got an 'Add custom block type' local action on the 'custom block library' tab (can be follow up).
Without that I think discoverability of the fact that block types exist and are fieldable is lost.
This is a new; and in my-opinion kick-ass feature of Drupal 8 that we're effectively burying as deep as the 'roles' tab or the 'user profile fields' tab in Drupal 7. And we deliberately hid the 'user profile fields' tab as deep as possible.
I think this also makes #1926294: Write tour integration for block_content.module more important
Comment #7.0
larowlanUpdated issue summary.
Comment #8
larowlanAdded #2078635: Add an 'Add custom block type' local action to the 'Custom block library' and updated issue summary accordingly
Comment #9
tim.plunkettYes. This does happen to terribly inconvenience custom block types. I think a new local action would be great.
Comment #10
Bojhan CreditAttribution: Bojhan commentedObviously we can't have an IA that is only accessible through the vertical menu. So that sounds fine to me, too. The labeling/descriptions for the custom block library worries me a little, but that can probably be a separate issue.
The patch worked on simplytest.me, so from a pure visual pov this seems RTBC
Comment #11
tim.plunkett#9: block-2078341-9.patch queued for re-testing.
Comment #12
tim.plunkettHelps me keep track
Comment #13
Gábor HojtsyThe code looks good as well. So adding this up with Bojhan's visual RTBC from #10, looks like good to go. I'm not sure about adding an "Add custom block type" local action on a page that does not deal with types, that sounds like an antipattern to me, but as people said above can/should be a followup to let this happen sooner.
Comment #14
Dries CreditAttribution: Dries commentedCommitted to 8.x. Thanks.
Comment #15
YesCT CreditAttribution: YesCT commentedcaused #2085603: Admin path of blocks changed, menus not prefixed with menu- anymore in config_translation
Comment #16
dcrocks CreditAttribution: dcrocks commentedThis UI is not working for me on Firefox 23.1 on OS X 10.6. Went to simplytest.me and did standard install of Core. The placement window is partially hidden by the toolbar. See attached. If I turn off Overlay, then the placement window is on top of the toolbar. Running on localhost, the placement window doesn't open at all.
Comment #17
dcrocks CreditAttribution: dcrocks commentedSorry, here are images.
Comment #18
Gábor Hojtsy@dcrocks: this patch did not introduce dialogs for such pages, this issue merely reorganized tabs. So not sure doing anything with this issue would help with your problem. (I *think* dialog displacement with the toolbar should work).
Comment #19
dcrocks CreditAttribution: dcrocks commentedOK, I checked on an older install, before this was committed, and it failed then as well. I need to find out when this broke.
Comment #20
tim.plunkettWhy?
#2058321: Move the 'place block' UI into the block listing added the usage of the modal, but it did not make the modal broken. The modal has always been broken.
Comment #21
dcrocks CreditAttribution: dcrocks commentedBecause I can't place a block if I can't access the form properly, unless I turn off features like overlay and/or toolbar. Is there a follow up to #2058321: Move the 'place block' UI into the block listing.
Comment #22
tim.plunkettYou can, for now, use your browser to open the link in a new tab, bypassing the modal. I was pretty sure there was a bug report for the modal not scrolling/resizing, but I can't find it. Feel free to open it, and link it here.
Comment #23
Gábor HojtsyOverlay does not participate in displaying the modal that you posted. Also overlay does support toolbar displacement, so as you place the toolbar in different orientations, it will adjust size. #2067263: Drupal dialog placement must take displacing viewport elements, like the Toolbar, into account when calculating placement is the issue you are looking for.
Comment #24
dcrocks CreditAttribution: dcrocks commentedThanx, I'll move over there.
Comment #25
tim.plunkettComment #26.0
(not verified) CreditAttribution: commentedUpdated issue summary.