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

file.xhtml restrict/Unrestrict not working after publish #3653

Closed
kevinworthington opened this issue Feb 28, 2017 · 4 comments
Closed

file.xhtml restrict/Unrestrict not working after publish #3653

kevinworthington opened this issue Feb 28, 2017 · 4 comments

Comments

@kevinworthington
Copy link
Contributor

From the file page, if a dataset owner attempts to restrict a file, the action doesn't take effect. This seems to only happen after a dataset has been published.

It seems the fix will simply require a change event from being triggered as occurs when setting a file to restricted from the dataset.xhtml page.

@pdurbin
Copy link
Member

pdurbin commented Feb 28, 2017

@kevinworthington thanks for the bug report. Can you please tell me which version of Dataverse you're running?

@kevinworthington
Copy link
Contributor Author

This issue was noticed with v. 4.6

@pdurbin
Copy link
Member

pdurbin commented Jun 23, 2017

I just suggested at #3776 (comment) that we re-test this issue when #3776 hits QA.

@pdurbin pdurbin added the User Role: Depositor Creates datasets, uploads data, etc. label Jul 4, 2017
@jggautier
Copy link
Contributor

In Dataverse 4.13, this bug seems to be fixed for restricting and unrestricting files from the file page:

  • In a published dataset, go to file page of a file that is not restricted
  • Click Edit > Restrict
  • See File Restrictions window and press Continue
  • Draft is created (Success message and green lock on file icon appear)
  • Go to dataset page and publish draft

Similar steps work for unrestricting files (no File Restrictions window, of course, and the lock disappears). I'm going to close this issue, but if I misunderstood what the bug is, please feel free to reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants