user1 created draft Node revision, user2 can see the revision when editing the published node

Created on 15 February 2024, 10 months ago
Updated 25 February 2024, 10 months ago

I have enabled the permission for anonymous user to "edit" the node and to create/save a new revision in draft format, after that, admin will review and publish the draft version of the node.

The problem I am having now is after anonymous user edit/save a new draft node revision, before admin publish the revision, at this time ,the second anonymous user "edit" the node, he/she will see the last revision draft version of the node but not the published version of the node. the second anonymous user should only see the published version of the node when editing but not the draft version which created by other user.

This is the process :

1: User1 create a node in draft
2: admin publish the node
3: User2 edit/save the node revision in draft version
4: User3 edit the published node before admin approve/publish last revision created by User2, in this moment, User3 can see/edit all the content added by User2 when on the "Edit" page.

πŸ’¬ Support request
Status

Active

Version

11.0 πŸ”₯

Component
Node systemΒ  β†’

Last updated 4 days ago

No maintainer
Created by

πŸ‡¬πŸ‡§United Kingdom freelylw

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.

  • Issue created by @freelylw
  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    That sounds like expected behaviour to me

  • πŸ‡¬πŸ‡§United Kingdom freelylw

    the revision created by User2 which has not been approved/published by admin, how come the User3/User4/User5.. can see it and edit it ? the User3/4/5/. should edit the published version and create their own revision.

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    There is only ever one draft - regardless of which user created it

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10
  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    Think of a scenario where an organisation has 2 editors.

    Editor one is working on a draft and saves some (unpublished) changes.

    Editor two then needs to edit, logically they build on top of Editor one's changes - not starting from the published state - otherwise you'd have endless conflicts at publish time - what is being published - editor one's changes or editor two's.

  • πŸ‡¬πŸ‡§United Kingdom freelylw

    what you saying is just one type of scenario, think about the wiki type, every user should only able to edit the published version but not an unpublished draft version from someone they don't know.

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    I'm telling you how Drupal works. Its not a scenario, its how default and forward revisions work by default. Workspaces module in core (experimental) does make changes to how that works to have a 'multiple forward revisions' landscape, but those are still shared across multiple users - but unique to a workspace. What you're describing is a whole new approach that is basically 'per-user' workspaces. I don't know if anything like that exists in contrib. I wouldn't recommend going down the path of trying to create something like that from scratch either - given how long Workspaces module has been experimental and how difficult it has been to get it this far.

Production build 0.71.5 2024