Add option to use latest revision instead of published revision

Created on 13 June 2022, over 2 years ago
Updated 28 March 2023, over 1 year ago

Problem/Motivation

We're using this module on a content type with content moderation, so we have draft versions of published nodes. The access check is against the published revision of the node, so if you add a new user to a draft version of the node, they don't get access until the draft is published.

This is completely expected and works as designed, but in our case we want to use the latest revision to determine access rather than the published one, so we have patched the module to achieve this.

Would you consider a patch that adds this as a configuration option? We are happy with the patch approach but thought it was worth asking.

Feature request
Status

Active

Version

2.0

Component

Code

Created by

🇦🇺Australia pameeela

Live updates comments and jobs are added and updated live.
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.

Production build 0.71.5 2024