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

After saving the Manage Files page without uploading any files, later it is not detecting the files when trying to upload #2387

Closed
Karthikeya212 opened this issue Oct 13, 2017 · 4 comments

Comments

Projects
None yet
5 participants
@Karthikeya212
Copy link
Collaborator

commented Oct 13, 2017

Descriptive summary

Server: spruce.dlib.indiana.edu
Testing: Regression
Browser: Chrome(61.0.3163.100 (64-bit))
Operating System: Windows10
Issue: After saving the Manage Files page without uploading any files, later it is not detecting the files when trying to upload.

Steps to reproduce

  1. Click on "Create Item" to start creating an item.
  2. It open the Manage Files page, do not upload any file and click on save and continue
  3. It navigates to Resource description page.
  4. Go back to Manage Files page and try to upload any file, it is returning "MediaObject invalid" error.
    mediaobject_invalid
@cjcolvar

This comment has been minimized.

Copy link
Member

commented Oct 16, 2017

This is the expected behavior now: Title and Publication Date (the required fields) and other metadata validations are skipped until you reach the Resource Description step then they apply even if you navigate back to the manage files step. This was to deal with #2045. At that time we did talk about the UX of entering data but then navigating away before saving and I mentioned this case in my PR (see point 2 in #2107 (comment)). If others think this issue needs to be revisited please say so otherwise I move to close this.

@joncameron

This comment has been minimized.

Copy link
Contributor

commented Oct 23, 2017

I'm going to move to close this too, although I'd like to have this in documentation somewhere for reference, and in case users bump into this edge case.

@mcwhitaker

This comment has been minimized.

Copy link

commented Nov 16, 2017

@joncameron Is this in documentation somewhere? Do we need a ticket to add it to documentation?

@joncameron

This comment has been minimized.

Copy link
Contributor

commented Nov 17, 2017

@mcwhitaker I've written a new story for it, #2460.

@mcwhitaker mcwhitaker added this to the Sprint 139 milestone Nov 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.