Problem/Motivation

In #1975064: Add more granular block content permissions we added new permissions for block content module
However the hook help entry still references the old administer blocks permission

Steps to reproduce

Creating and managing block types
Users with the Administer blocks permission can create and edit block types with fields and display settings, from the Block types page under the Structure menu. For more information about managing fields and display settings, see the Field UI module help and Field module help.
Creating content blocks
Users with the Administer blocks permission can create, edit, and delete content blocks of each defined block type, from the Content blocks page. After creating a block, place it in a region from the Block layout page, just like blocks provided by other modules.

Proposed resolution

Update the help text to be more appropriate to the new permissions

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3352550

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

larowlan created an issue. See original summary.

rckstr_rohan made their first commit to this issue’s fork.

rohan-sinha’s picture

Status: Active » Needs review

created a MR, as per the new administer block content permission, pls review, suggestions are welcomed.thanks

amietpatial’s picture

Changes look good to have suggestions on if "manage" can be replaced by "configure" in the sentence just to be more specific and also being used inside the block layout page "The Custom Block module allows you to create, manage and delete custom block types and content-containing blocks."

smustgrave’s picture

Status: Needs review » Needs work

These don't appear to be the suggestions @larowlan was looking for.

New permissions were added but they were not mentioned in the MR.

Rassoni made their first commit to this issue’s fork.

rassoni’s picture

Status: Needs work » Needs review
aaronmchale’s picture

Status: Needs review » Needs work

We definitely need to describe each new permission that was added. I would suggest adding a bulleted list with each new permission and a description of what it does. Note that the permissions are now per block type, so that should also be clearly described.

rkoller’s picture

re #9 i am not sure if it would be necessary to describe each new permission on the help page. those help pages are about the functionality available within a module not about each settings option and available permissions in particular (https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...). if you compare it with the help page of the node module permissions are summarized in one dedicated point:

User permissions
The Node module makes a number of permissions available for each content type, which can be set by role on the permissions page.

aside that permissions are only mentioned in some of the others points.

but aside the points in the uses section i would definitely update the about section as well. removing the link to the custom block module documentation. it is basically more or less the same as the current help page for the block content module: https://www.drupal.org/documentation/modules/block_content. therefore it is sort of redundant information.
but on the other hand i would also add one important piece of information to the about section. that you are able to create content blocks in two locations within the drupal admin interface. content blocks created in /admin/content/block (the new path) are reusable content blocks and content blocks created within layout builder are none reusable content blocks aka inline block (or what name will be agreed on in #3318558: Adjust the block terminology in Layout Builder to align with block and block_content changes). but i consider that detail not well documented and clear to the user. me for example i've learned and understood it completely in the course of the whole reorganizing the block items issue. and it is also something that wasn't clear to everyone who has attended the feedback sessions in the different user groups i've visited.

larowlan’s picture

Left some suggestions in the MR

Will need a rebase now the rename issue is in

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

acbramley made their first commit to this issue’s fork.

acbramley changed the visibility of the branch 11.x to hidden.

acbramley changed the visibility of the branch 3352550-hook-help-for to hidden.

acbramley’s picture

Status: Needs work » Needs review

This was extremely out of date, some of these sections were moved to Help topics. I've attempted to apply the relevant suggestions from https://git.drupalcode.org/project/drupal/-/merge_requests/3806 to a new MR against 11.x

I think it would be good to quickly get something in that may not be perfect so we can remove references to old permissions/naming ASAP and then iterate on wording later.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

Thanks for picking this up.

Reviewed the changes and they appear correct to me. Don't need tests for help text.

nod_’s picture

Status: Reviewed & tested by the community » Needs work

the wording need a little bit more work, let's try to get a native, documentation-inclined person to help out

acbramley’s picture

Issue tags: -Novice

Removing Novice tag based on #20

acbramley’s picture

Status: Needs work » Needs review

The sentence in question doesn't seem to belong in block content's help anyway so IMO we can just remove that therefore this is back to NR.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

LGTM

  • alexpott committed 0e61b8c8 on 11.x
    Issue #3352550 by acbramley, rassoni, rohan-sinha, larowlan, smustgrave...
alexpott’s picture

Status: Reviewed & tested by the community » Fixed

Committed 0e61b8c and pushed to 11.x. Thanks!

Not backporting to 11.2.x because this is a string change.

Should this be backported to 10.6.x?

Status: Fixed » Closed (fixed)

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