-
Notifications
You must be signed in to change notification settings - Fork 490
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
Comments
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;| |
@djbrooke and I discussed this issue this morning and he said he'd check in with @donsizemore about it. |
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! |
Hi Danny, I don't think it's a huge issue, but it's unexpected behavior, and I was dutifully reporting it. Thank you! |
Stephen mentioned how to test, "have a custom metadata block and then change it back to root and all good things happen." |
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. |
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. |
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.
The text was updated successfully, but these errors were encountered: