Private and unpublished nodes

Created on 28 March 2024, 6 months ago
Updated 13 April 2024, 6 months ago

With the last update, the nodes marked as private must be also set "published" to be viewable by who has only "Access private content permission".
Previously, the "published" field wasn't involved and only nodes created after the update have this issue.
This can cause big problems to some reserved areas like mine, where by default all the private nodes are set unpublished and the published field is hidden in the form.

I know that node grants can be tricky, but I think it would be better to specify what has changed in the 2.1 release notes or some websites can stop working as expected.

Feature request
Status

Closed: won't fix

Version

2.1

Component

Documentation

Created by

🇮🇹Italy Cheope

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

Merge Requests

Comments & Activities

  • Issue created by @Cheope
  • First commit to issue fork.
  • 🇬🇧United Kingdom adamps

    AdamPS changed the visibility of the branch 3436717-private-and-unpublished to hidden.

  • Status changed to Closed: won't fix 6 months ago
  • 🇬🇧United Kingdom adamps

    The release note was deliberately vague because it's a security fix so we avoid making it too obvious how to exploit it. The previous behaviour was a bug, it should never have been like that. I understand that this caused inconvenience for you however it was pure chance that your site previously worked. By default unpublished nodes aren't accessible and this module (now correctly) doesn't change that.

Production build 0.71.5 2024