#24829 closed defect (bug) (fixed)
Don't allow users to restore a revision if the post is locked
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 3.6 | Priority: | normal |
Severity: | normal | Version: | 3.6 |
Component: | General | Keywords: | needs-patch |
Focuses: | Cc: |
Description
Currently a user that's locked out of a post by our AMAZING new post locking, can still restore a revision of that post. It would be nice to let them browser revisions, but we should prevent them from restoring one while someone else has the post locked.
Attachments (3)
Change History (14)
#2
in reply to:
↑ 1
@
10 years ago
Replying to adamsilverstein:
seems like users should be kicked out the revisions screen if another user takes over the post lock.
Honestly, I'd rather that they be allowed into the revisions screen and even be able to browse revisions, but not be allowed to restore (remove the UI for it, or replace it with a short "post is locked" message).
Also, when a lock is taken from someone and they are kicked out, the last thing that happens is an autosave that we do for them before we kick them. I'm wondering if it might be a good idea to have a button on the lock taken dialog that offers to send them to their latest autosave in revisions? Thoughts? Here's the dialog:
@
10 years ago
disable restore button when post locked, disallow restore if locked (while on revisions screen)
#3
follow-up:
↓ 4
@
10 years ago
24829.2.diff disables the existing button instead of using a different one with a new string.
#4
in reply to:
↑ 3
@
10 years ago
Replying to aaroncampbell:
24829.2.diff disables the existing button instead of using a different one with a new string.
ah simplicity! I forgot - no new strings! We can add better/live post-locking info on the revisions screen in the future.
#5
follow-up:
↓ 6
@
10 years ago
24829.diff just puts the Backbone disabled rendering in a PHP else so that we don't get double disabled=disabled happening in the case of a current revision of a post that is also being edited by someone else.
#6
in reply to:
↑ 5
;
follow-up:
↓ 7
@
10 years ago
Replying to markjaquith:
24829.diff just puts the Backbone disabled rendering in a PHP else so that we don't get double disabled=disabled happening in the case of a current revision of a post that is also being edited by someone else.
tested & works as expected.
#7
in reply to:
↑ 6
@
10 years ago
Replying to adamsilverstein:
Replying to markjaquith:
24829.diff just puts the Backbone disabled rendering in a PHP else so that we don't get double disabled=disabled happening in the case of a current revision of a post that is also being edited by someone else.
tested & works as expected.
Assuming you tested .3.diff not just .diff?
#8
@
10 years ago
What if the current user has the lock? As in, they opened "Browse" in a new window? What happens if they try to restore something with the editor open? (Just curious.)
interesting - nice catch! seems like users should be kicked out the revisions screen if another user takes over the post lock.