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

re-checking "use metadata fields from root dataverse" doesn't save, disables further editing #3427

Closed
donsizemore opened this issue Oct 25, 2016 · 7 comments

Comments

@donsizemore
Copy link
Contributor

Thu-Mai and Sophia are experiencing what appears to be the 2nd half of #2757 - our "use metadata fields from the UNC Dataverse" checkbox is currently UN-checked, and they want to check it. They then experience the symptoms described in #2757: no confirmation of saved changes, and the edit drop-down widget no longer works for that session. A page refresh returns that the changes are not saved.

We're running 4.5 on RHEL 7.2; I checked the resolved issues in 4.5.1 but didn't see a similar ticket.

@donsizemore
Copy link
Contributor Author

Just a note that I've duplicated this behavior on our nearly-squeaky-clean dataverse-test.irss.unc.edu (4.5) and on another local dataverse instance running 4.5.1.

The only possibly pertinent entry I see in the Glassfish log is

WARNING|glassfish 4.1|javax.enterprise.resource.webcontainer.jsf.flash|_ThreadID=50;_ThreadName=jk-connector(3);_TimeMillis=1477404199227;_LevelValue=900;_MessageID=jsf.externalcontext.flash.response.already.committed;|
JSF1095: The response was already committed by the time we tried to set the outgoing cookie for the flash. Any values stored to the flash will not be available on the next request.|#]

@pdurbin
Copy link
Member

pdurbin commented Dec 15, 2016

@djbrooke and I discussed this issue this morning and he said he'd check in with @donsizemore about it.

@djbrooke
Copy link
Contributor

Hi @donsizemore - I know that you guys are up and running on Dataverse 4, so I wanted to check in with you to see if this issue was resolved or if you just used a workaround. I'll check in with you after the break as well. Thanks!

@donsizemore
Copy link
Contributor Author

Hi Danny, I don't think it's a huge issue, but it's unexpected behavior, and I was dutifully reporting it. Thank you!

@pdurbin pdurbin added the UX & UI: Design This issue needs input on the design of the UI and from the product owner label Jun 8, 2017
@pdurbin pdurbin added the User Role: Curator Curates and reviews datasets, manages permissions label Jul 4, 2017
@djbrooke djbrooke removed their assignment Oct 24, 2018
@pdurbin pdurbin removed UX & UI: Design This issue needs input on the design of the UI and from the product owner User Role: Curator Curates and reviews datasets, manages permissions labels Nov 16, 2018
@sekmiller sekmiller self-assigned this Nov 19, 2018
@sekmiller sekmiller self-assigned this Nov 27, 2018
@kcondon
Copy link
Contributor

kcondon commented Dec 4, 2018

Stephen mentioned how to test, "have a custom metadata block and then change it back to root and all good things happen."

@kcondon
Copy link
Contributor

kcondon commented Dec 5, 2018

So more specifically, if you have custom metadata blocks defined in the system (we do), create a dataverse, uncheck Use metadata fields from Root, save. Go back, recheck use metadata fields from Root, save, edit button is temporarily disabled until refresh and if you double check the dv, the use metadata fields from Root remained unchecked -it didn't save.

@kcondon
Copy link
Contributor

kcondon commented Dec 5, 2018

OK this works -I'm able to recheck use metadata fields from root and it saves. Note that when the checkbox is checked, the save happens from the popup and not the page.

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

5 participants