A critical usability issue with Drupal 8 block UI arose in the process of building the new Drupal.com. The site builder, a drupalist with many years of experience working with Drupal 5, 6, and 7 created a custom block and then could not figure out where to go to edit it. She hunted around in th UI for more than half an hour (!) before finally giving up and coming to me for help.

Before just giving her the answer I asked her to walk through her process. Here is what she did.

  • Opened structure
  • Opened block layout
  • Clicked "Create custom block"
  • Built a new custom block (hand coded HTML)
  • Saved the block, placed in a region with visibility settings for a specific page
  • Later returned to block layout and found the block
  • Clicked "configure"
  • Saw no option to edit the HTML she had entered
  • Started hunting around for where to do this
  • Did not look in "custom block library" because that did not "seem like a place to edit things"

A simple solution would be to add to the drop-button: "edit original, edit parent" or some other text that indicates to the user both "go here to edit the content" and "this will bring you to the "parent" of this item".

Later on save we can say ""The content will be changed for all instances of this block not just [block instance name]."

CommentFileSizeAuthor
#12 Selection_001.png57.36 KBraj45

Comments

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented

Contextual links are an option here too, which were once working

dawehner’s picture

dawehner
Primary language German
commented
Version: 8.0.0-alpha14 » 8.0.x-dev
Component: block.module » custom_block.module
Status: Needs work » Active

One small step would be to start moving the custom block paths under admin/structure/block, so for example have admin/structure/block/custom/add , just as idea. This is where I looked at, first time I saw that issue.

I don't see how this would block the release, Drupal is not totally impossible to use:

Issues that have significant repercussions but do not render the whole system unusable (or have a known workaround) are marked major.

Corrected the issue metadata

tkoleary’s picture

tkoleary commented
Priority: Critical » Major

I don't see how this would block the release, Drupal is not totally impossible to use:

Changed to Major

dawehner’s picture

dawehner
Primary language German
commented

@tkoleary
I didn't wanted to sound harsh earlier, I think this discoverability issues are a huge deal, even for power users.

There used to be an issue which solved the problem for multiple various blocks (#1956134: Provide helpful editing links on "admin/structure/block" for deriver blocks (menu, views, block content, etc.)):

  • a menu block => menu listing
  • a views block => views editing

your proposed solution in the patch sounds perfect! On top of that the configure block form could
also link to the corresponding edit form. There is a similar approach for that in the views block already.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented

+1 to the 'provide helpful editing links issue'

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Status: Active » Postponed

blocked on #1956134: Provide helpful editing links on "admin/structure/block" for deriver blocks (menu, views, block content, etc.)

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Related issues: +#1956134: Provide helpful editing links on "admin/structure/block" for deriver blocks (menu, views, block content, etc.), +#2302563: Access check Url objects
larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Title: Where to edit the contents of a custom block is not discoverable » [PP-2] Where to edit the contents of a custom block is not discoverable
askibinski’s picture

askibinski commented

related: #1164718: Improving the usability between "custom block" and "content"

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Title: [PP-2] Where to edit the contents of a custom block is not discoverable » [PP-1] Where to edit the contents of a custom block is not discoverable
webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Component: custom_block.module » block_content.module
raj45’s picture

raj45 commented
StatusFileSize
new Selection_001.png57.36 KB

Under "Structure" > "Block layout", you can only edit a block's Title, Visibility and Region under "Configure block", so the only apparent access to editing the Body-field of a custom block is the quick-edit links, when viewing a page, by clicking on the pencil-icon and selecting "Edit".

I suppose it isn't possible to include the Body-field of a custom block at the top if you click on "Configure" on the "Block Layout", since that would be the most user-friendly?

A possible solution would be to add an "Edit"-link along with the "Configure block". See the image:

new edit button

tkoleary’s picture

tkoleary commented

@raj45

+1 to adding "edit" link

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
commented

This issue says it's blocked on #1956134: Provide helpful editing links on "admin/structure/block" for deriver blocks (menu, views, block content, etc.), but there hasn't been any activity on that issue since September. Is that still really true? Is this something we could do on its own if there's no longer motivation to address that larger issue?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

tkoleary’s picture

tkoleary commented

@rootwork

IMO this is still an important usability issue. We have added contextual links to these blocks on the front end (quickedit and edit custom block, edit menu, edit view etc.). I see no reason why we should not just match those exactly in the place block UI.

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
commented

@tkoleary I agree, and I guess I'm confused why this is being blocked by another issue where there is no work being done on it. It seems like we could still do things here.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Title: [PP-1] Where to edit the contents of a custom block is not discoverable » Where to edit the contents of a custom block is not discoverable
Version: 8.1.x-dev » 8.2.x-dev
Status: Postponed » Active

Yeah, I don't quite understand that either. Back to active unless a bit more rationale could be provided.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented

#1956134: Provide helpful editing links on "admin/structure/block" for deriver blocks (menu, views, block content, etc.) provides this edit links including an edit link for block content - i.e what is proposed in #12

This issue is a 'once off' fix for just block content, that one is a fix for menus, views and other blocks too.

I think we should be focused on the other one.

In fact I don't think this one should be postponed on it, I think it should be closed as a duplicate (my 2c).

There is no code or patches here, there are several over there.

Thoughts?

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

danchadwick’s picture

danchadwick commented

Additional data point. Been a drupal developer since d6. I couldn't find the link (unless google found this issue). Also, very disappointed that custom blocks aren't config and can't be deployed as such.

skaught’s picture

skaught
Primary language English
commented

have added Drupal9 tag to 1956134. give it attention.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Status: Active » Closed (duplicate)

After reading https://www.drupal.org/project/drupal/issues/1956134 and this I agree with @larowlan that this a duplicate and all effort should be applied to https://www.drupal.org/project/drupal/issues/1956134

If anyone disagrees please open with a justification.

Thanks!