Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Applying remote publish change could mark nodes as unchanged #4138

Closed
bjester opened this issue Jun 13, 2023 · 0 comments · Fixed by #4580
Closed

Applying remote publish change could mark nodes as unchanged #4138

bjester opened this issue Jun 13, 2023 · 0 comments · Fixed by #4580
Assignees
@akolson
Labels
DEV: backend P0 - critical Priority: Release blocker or regression
Milestone
Studio: Bulk Edit...

Comments

@bjester
Copy link
Member

bjester commented Jun 13, 2023

Changes are returned to all other clients other than the originator when the change has been applied. So if 2 users are editing a channel, and one publishes the channel, the other user's edits could be marked unchanged

This was pre-existing - but it's just occurred to me that this could mark content nodes are published that are not, if changes have been applied to them since the publish event was submitted.

Don't think we need to unpick this now, but might be good to have a follow up issue.

Originally posted by @rtibbles in #4113 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@akolson akolson

Labels
DEV: backend P0 - critical Priority: Release blocker or regression
Projects
None yet
Milestone
Studio: Bulk Editing Release
Development

Successfully merging a pull request may close this issue.

Update publish logic with edge case akolson/studio
2 participants
@bjester @akolson