allow section maintainers access to unpublished nodes in their section

Created on 15 December 2023, about 1 year ago
Updated 17 May 2024, 8 months ago

As a release manager I need to be able to work on the unpublished release highlights. The current on is for Drupal 10.2.0 โ†’ to which I get a 403.

The same is true for unpublished release notes.

Can you update my access?

Also, let me know what the role is so we can document this in the release manager documentation.

Thanks

๐Ÿ“Œ Task
Status

Active

Version

3.0

Component

Code

Created by

๐Ÿ‡ณ๐Ÿ‡ฟNew Zealand quietone

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @quietone
  • ๐Ÿ‡ณ๐Ÿ‡ฟNew Zealand quietone
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States xjm

    Just confirming that @quietone should have access to unpublished blog posts (and possibly other similar content access bundled with whatever approriate d.o role). She is a Drupal core release manager, and as such is already trusted with the integrity of the entire core project. Being able to create, view, and edit unpublished Drupal core blog posts is a needed part of our release management responsibilities. Thanks!

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น

    As site moderator, I get a 403 error on https://www.drupal.org/blog/drupal-10-2-0 โ†’ too.

    It seems that the roles with the bypass node access permission are the security team or association staff roles. That permission has been removed from the Site moderator role and others.

    There are some view any unpublished [content type] content permissions, but not a view any unpublished blog content permission. Those permissions are not given to any account, though.

  • ๐Ÿ‡ณ๐Ÿ‡ฟNew Zealand quietone

    @apaderno, thanks for the explanation. It seems rather final. Is there not a plan to address this, so that I can fulfill all aspects of my role?

    I also have no access to unpublished release notes.

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น

    @quietone Since there are permissions to see unpublished nodes of specific content types, I guess the plan was/is to give them to the right roles.
    This needs to be handled by Drupal.org Association staff, like @drumm or @fjgarlin (for example), who are the ones to commit code on the repositories for drupal.org modules/themes.

  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น
  • ๐Ÿ‡ฎ๐Ÿ‡นItaly apaderno Brescia, ๐Ÿ‡ฎ๐Ÿ‡น

    (As a side note, https://www.drupal.org/blog/drupal-10-2-0 โ†’ has been published. This request is still valid, though, as quietone should have access to any unpublished blog.)

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States B_man California, USA

    I think the right role here is Content Administrator, since I don't see anything more specific I'm going to go ahead and grant it. If it turns out not to be the right role, we might swap it for the more correct one.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States B_man California, USA

    Content administrator has been granted to quietone. Please check when you have a chance that you can see what you need for doing release manager duties and report back if there's still a hangup.

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States drumm NY, US

    I think this might need to be revised to a drupalorg module task: allow section maintainers access to unpublished nodes in their section

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States drumm NY, US

    Bypass node access is an overly-broad permission that has proven to be problematic. Thereโ€™s no indication of what lines shouldnโ€™t be crossed, so people with that access can unknowingly cause problems.

    We do have a โ€œPost: View any unpublished contentโ€ permission that is not currently granted to any role. That could be a quick fix.

    However, โ€œallow section maintainers access to unpublished nodes in their sectionโ€ solves this for all section maintainers, and does not require figuring out which roles are right just for someone helping with a section.

  • ๐Ÿ‡ณ๐Ÿ‡ฟNew Zealand quietone

    @B_man, I don't know of any unpublished blog posts so I can't check if I can access one.

    Can someone explain what the 'sections' are and how that applies to the different core committer roles?

  • ๐Ÿ‡ณ๐Ÿ‡ฟNew Zealand quietone
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States drumm NY, US

    https://www.drupal.org/about/core โ†’ & https://www.drupal.org/community/event-organizers โ†’ are examples of sections, which are implemented with organic groups. This allows us to set up permissions for section maintainers within their section, without granting excessive access throughout the rest of the site.

Production build 0.71.5 2024