Permission denied to create content unless users have the "View published content" permission

Created on 1 November 2016, almost 9 years ago
Updated 27 August 2025, about 2 months ago

Problem/Motivation

A user might have the permission to create new nodes, for example:
Article: Create new content

But if it doesn't have the "View published content" permission.
From a site builder perspective doesn't make much sense to have this two permission so tied.

We ran into this problem while evaluating workarounds for
✨ Move permission "view any unpublished content" from Content Moderation to Node Postponed

The first thing that the access controller does is to check for the "View published content" permission and denies access immediately if the user doesn't have it

Proposed resolution

Change the logic of the access controller to give access to create a node if the user has permission to do so.

Remaining tasks

Evaluate if this can go in D8 or it might break sites. D8 might add at least an explanation that "View published content" permission is required to create nodes.

User interface changes

None.

API changes

None.

Data model changes

None.

✨ Feature request
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

user system

Created by

πŸ‡ͺπŸ‡ΈSpain rodrigoaguilera Barcelona

Live updates comments and jobs are added and updated live.
  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

  • πŸ‡ͺπŸ‡ΈSpain rodrigoaguilera Barcelona

    I don't maintain any projects that require this anymore so it can be closed from my point of view

Production build 0.71.5 2024