Users with just create content permission don't know publishing status

Created on 15 June 2017, almost 8 years ago
Updated 24 March 2025, 15 days ago

Problem/Motivation

Ever since time began it has been confusing for users who don't have the "Administer Content" (aka "Administer nodes") permission, because they don't see if saving a new node will publish it or not.

Proposed resolution

If the user doesn't have permission to change the publishing status, make them aware of what will happen when they click save.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

11.0 🔥

Component
Node system  →

Last updated about 2 hours ago

No maintainer
Created by

🇬🇧United Kingdom timmillwood 🏴󠁧󠁢󠁷󠁬󠁳󠁿 Wales, UK

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇸🇮Slovenia alesr

    I stumbled upon a related issue to this one.

    Simple scenario: specific user role needs to be able to Publish/Unpublish one specific content type.

    I don't understand why this cannot be added as permission which would solve this issue too.

    Instead of giving this user role the whole "Administer content" permission with all the caveats which apply to all content types and/or setting $form['status']['#access'] = TRUE;
    in the form_alter.

  • First commit to issue fork.
  • 🇦🇺Australia acbramley

    I think the disabled checkbox with description text makes a lot of sense, it also follows patterns we already have in other areas such as how ModerationHandlers disabled the Create new revision checkbox.

    The last patch contained a huge amount of unrelated code so I'm spinning up an MR with just the NodeForm change.

    We also need to specifically check the permission so we don't surface the checkbox when content_moderation is installed (i.e we don't want to change content_moderation's NodeAccessTest.

    MR going up to see what issues this may cause

  • Pipeline finished with Failed
    15 days ago
    Total: 569s
    #456683
  • 🇦🇺Australia acbramley

    We only had 1 test failure which wasn't for the status checkbox, but the Published status in the meta information. I've fixed that and added additional test coverage for the checkbox

  • Pipeline finished with Success
    15 days ago
    Total: 718s
    #456708
Production build 0.71.5 2024