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

Cannot edit file versions #295

Closed
2 of 4 tasks
chrisdaaz opened this issue Aug 15, 2017 · 3 comments
Closed
2 of 4 tasks

Cannot edit file versions #295

chrisdaaz opened this issue Aug 15, 2017 · 3 comments
Labels

Comments

@chrisdaaz
Copy link

Severity

Is the production site running?

  • yes
  • no

Are staff blocked from performing their work?

  • yes
  • no

Descriptive summary

Reported by a faculty member:

Users are unable to edit the version of a file (i.e. swapping out an old version of a file with a new one).

I recreated the bug with this work on staging: https://nufiaweb-s.library.northwestern.edu/concern/generic_works/t435gc99f?locale=en

Expected behavior

When a user attempted to change the version of a file, the new version of the file should be available:

image

Actual behavior

The old version remains, despite the metadata changing to reflect the new version:

image

Steps to reproduce the behavior

  1. Go to https://nufiaweb-s.library.northwestern.edu/concern/generic_works/t435gc99f?locale=en
  2. Download a file
  3. Change the file and save it to your computer
  4. Attempt to replace the file with the new version (select actions > versions)
  5. Upload the new version of the file
  6. Save
  7. Reopen the file from the work page and see if it's the new version.
@chrisdaaz
Copy link
Author

i'm not seeing this bug reported in hyrax (maybe there's an issues but it's in dev-speak?), but perhaps relevant to #293

@csyversen
Copy link

so versioning works on my local development environment, but not in staging or production. it points to a configuration error as opposed to a code error. I've been looking into this though!

@chrisdaaz
Copy link
Author

this is working now, might have been a configuration thing that was resolved with the move to aws.

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

No branches or pull requests

2 participants