Bug 30361 - If bug 29369 is applied or an update to 21.11.03 occurs no item saving is permitted if the framework marks this field as mandatory.
Summary: If bug 29369 is applied or an update to 21.11.03 occurs no item saving is per...
Status: RESOLVED DUPLICATE of bug 30717
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 21.11
Hardware: All Linux
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-25 15:11 UTC by Courtenay Johnson
Modified: 2022-06-19 11:46 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Courtenay Johnson 2022-03-25 15:11:38 UTC
When I upgraded from 21.05.03 to 21.11.03 I found when adding an item using the book framework it would refuse to save the net item. It instead displayed a popup that stated a mandatory field was blank. It does not provide any visual indication as to which field is the problem. (I have 6 visible mandatory fields)

I determined that the specific field that was causing the problem had the dateaccessioned.pl plugin and is the 952$d. The date picker does generate a date which looks normal, but the item just can’t be saved.
 
When I edited the framework to make this field not mandatory, then I can save newly created or edited items. The date in the picker is shown correctly in the display of the saved item.

In 21.05.03 there was no problem. I read bug 29369 and examined the code and this had been applied in 21.11.03.
The workaround is totally acceptable to me and works fine with no other issue noticed so far.
Comment 1 Katrin Fischer 2022-06-19 11:46:14 UTC
Hi Courtenay, I believe this is bug 30717, I've tried to alert our RMaints that it still needs backporting to 21.11.

*** This bug has been marked as a duplicate of bug 30717 ***