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

Selecting a community after entering metadata wipes content of fields #1892

Closed
fenekku opened this issue Sep 23, 2022 · 6 comments
Closed

Selecting a community after entering metadata wipes content of fields #1892

fenekku opened this issue Sep 23, 2022 · 6 comments
Labels
bug Something isn't working

Comments

@fenekku
Copy link
Contributor

fenekku commented Sep 23, 2022

Package version (if known): 9.1 (also on demo stie at time of writing which seems to be running what will be v10)

Describe the bug

When filling out metadata for a new upload with file and then selecting a community, some of the filled metadata fields are wiped.

Steps to Reproduce

  1. Go to /uploads/new
  2. Upload a file
  3. Fill out required fields
  4. Select community to associate with the record
  5. See wiped fields
  6. Try to upload anyway
  7. even more weirdness

Expected behavior

You can choose what community to associate with the record at any point in the process of filling out the record and it won't cause issues.

Other context

It looks like choosing a metadat-only upload doesn't have this problem.

@fenekku fenekku added the bug Something isn't working label Sep 23, 2022
@fenekku fenekku changed the title Selecting a community after entering metadata wipes field content Selecting a community after entering metadata wipes content of fields Sep 30, 2022
@github-actions
Copy link
Contributor

This issue was automatically marked as stale.

@github-actions github-actions bot added the stale No activity for more than 60 days. label Nov 30, 2022
@fenekku fenekku removed the stale No activity for more than 60 days. label Nov 30, 2022
@github-actions
Copy link
Contributor

This issue was automatically marked as stale.

@github-actions github-actions bot added the stale No activity for more than 60 days. label Jan 30, 2023
@fenekku fenekku removed the stale No activity for more than 60 days. label Jan 30, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2023

This issue was automatically marked as stale.

@github-actions github-actions bot added the stale No activity for more than 60 days. label Apr 1, 2023
@fenekku fenekku removed the stale No activity for more than 60 days. label Apr 3, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jun 3, 2023

This issue was automatically marked as stale.

@github-actions github-actions bot added the stale No activity for more than 60 days. label Jun 3, 2023
@fenekku fenekku removed the stale No activity for more than 60 days. label Jun 5, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Aug 5, 2023

This issue was automatically marked as stale.

@github-actions github-actions bot added the stale No activity for more than 60 days. label Aug 5, 2023
@fenekku fenekku removed the stale No activity for more than 60 days. label Aug 7, 2023
@fenekku
Copy link
Contributor Author

fenekku commented Apr 1, 2024

Seems to have been fixed on Zenodo sandbox so assuming fixed on v12.

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
Status: Done
Development

No branches or pull requests

1 participant