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.

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

permissions error trying to delete a document because it wants to delete the associated log entry #371

Closed
4 tasks done
rlskoeser opened this issue Nov 18, 2021 · 2 comments
Assignees
Labels
🐛 bug Something isn't working

Comments

@rlskoeser
Copy link
Contributor

rlskoeser commented Nov 18, 2021

testing notes

go to the document admin list on the test site and choose one to delete

  • confirm the delete review screen doesn't complain about permissions
  • confirm the delete review screen includes language about suppressing and merging documents in preference to deleting
  • confirm you are actually able to delete the object
  • go to the log entries admin list and confirm there is a new log entry for the deletion

Error has been reported by both Alan and Marina

01C2D919-22C0-4F62-888C-802C9B2D2F47

Normally we'll want to suppress or merge documents rather than deleting, but it should be possible for content editors to delete them when the need arises.

@rlskoeser rlskoeser added the 🐛 bug Something isn't working label Nov 18, 2021
@rlskoeser rlskoeser added this to the PGP v4.0 (MVP) milestone Nov 18, 2021
@kmcelwee kmcelwee self-assigned this Jan 3, 2022
@kmcelwee kmcelwee removed their assignment Jan 3, 2022
blms added a commit that referenced this issue Jan 5, 2022
@rlskoeser rlskoeser self-assigned this Jan 5, 2022
@richmanrachel
Copy link

Draft for custom language for admin delete:
Are you sure this document should be deleted? Please only delete documents created in error. Non-documentary sources should be suppressed. Duplicates should be merged. Thanks for keeping our database safe and clean!

@rlskoeser rlskoeser added the 🗜️ awaiting testing Implemented and ready to be tested label Jan 11, 2022
@richmanrachel
Copy link

@rlskoeser - Perfect! And we also confirmed that it doesn't screw with the existence of the fragment (tested with both T-S 20.117 and BL OR 5566B.23).

@richmanrachel richmanrachel removed the 🗜️ awaiting testing Implemented and ready to be tested label Jan 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants