When creating a new notice if I choose my branch and then the module the branch changes back to 'all libraries'. I then change the branch back to mine and enter the code and text and have everything in place and hit save. When I save it doesn't save. The notice is lost. Right now you have to create the notice for 'all libraries' and then copy the notice to my library and then delete the 'all libraries copy'.
Is this the same as what's fixed in bug 10439 ?
I cannot reproduce on master.
Part of the problem here is that the page reloads when you change the module after selecting the branch. A first fix to avoid more confusion would be switching the order of the fields and put the module first. A better solution would be to avoid the reloading.
Actually, the reloading permits to refresh the fields list. I think we should keep this behavior.
I thnk avoiding the page reload will require more work - like using Ajax to reload only the field list. Switching the field order could help a bit to make it less irritating.
(In reply to Nicole C. Engard from comment #0) > When creating a new notice if I choose my branch and then the module the > branch changes back to 'all libraries'. Confirmed. If changing the module reloads the page without warning we might do fix it a number of ways: - Use Ajax to reload only the field list as Jonathan suggests - Convert the "New notice" button to a menu which lists the possible module choices - Add an intermediate step where you must submit a module choice before rest of the form displays. > When I save it doesn't save. The notice is lost. I cannot reproduce this problem. Please test again in master. If the problem can't be reproduced I suggest we close this bug and create a new one for the module-switching problem.
I can't reproduce the problem with the form not saving either. I files a new bug 14358 for the refreshing of the page when changing the module.ill file