Skip to content

8599 legacy template issue#8789

Merged
kcondon merged 2 commits intodevelopfrom
8599-legacy-template-issue
Jun 9, 2022
Merged

8599 legacy template issue#8789
kcondon merged 2 commits intodevelopfrom
8599-legacy-template-issue

Conversation

@scolapasta
Copy link
Contributor

What this PR does / why we need it:
adds a flyway script fix some legacy templates

Which issue(s) this PR closes:

Closes #8599

Special notes for your reviewer:
none

Suggestions on how to test this:
find a legacy template (or create one by removing the id in the termsofuseandaccess column), set the default template for the dv to use that template. Verify that trying to create a dataset there causes a 500 error. Then run script (e.g. deploy this branch) and see that the issue is fixed.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:
no

Is there a release notes update needed for this change?:
yes, included

Additional documentation:

@scolapasta scolapasta added this to the 5.11 milestone Jun 9, 2022
@sekmiller sekmiller self-assigned this Jun 9, 2022
@sekmiller sekmiller removed their assignment Jun 9, 2022
@kcondon kcondon self-assigned this Jun 9, 2022
@kcondon kcondon merged commit a324b51 into develop Jun 9, 2022
@kcondon kcondon deleted the 8599-legacy-template-issue branch June 9, 2022 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

500 server error when adding a dataset in dataverse where default template has no associated terms

3 participants