Bug 30659 - Date acquired is not working in 21.11
Summary: Date acquired is not working in 21.11
Status: RESOLVED DUPLICATE of bug 30717
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: 21.11
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-02 04:25 UTC by NAYEMA NASRIN
Modified: 2022-05-31 09:42 UTC (History)
4 users (show)

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


Attachments
A cross mark in the field of Date Acquired (178.62 KB, image/png)
2022-05-02 04:25 UTC, NAYEMA NASRIN
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NAYEMA NASRIN 2022-05-02 04:25:07 UTC
Created attachment 134452 [details]
A cross mark in the field of Date Acquired

I have recently upgraded the Koha version from 17 to 21.11. From then the date acquired(952$d) option is not working. It is a mandatory field and even if I select date it says this field is empty. I tried to change the marc framework so that I can make this field optional but it doesn't accept any changes. It gives error. Also I have seen date is creating a problem in entire KOHA 21.11. It is a very important field because I am not able to generate report without any date.
Comment 1 Katrin Fischer 2022-05-02 09:53:43 UTC
Can you please check if there is another subfield that is marked manadatory and set to hidden in the form? I am not sure that date accessioned is the problematic field here as the pop-up alert doesn't display the field name.
Comment 2 NAYEMA NASRIN 2022-05-06 05:55:31 UTC
Thanks for your prompt reply. I read bug no 30361 and I am having the same problem. When I upgraded from 17 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 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 not save the framework, it gives error. I think dateaccessioned.pl plugin throws the error.

Recently I have deleted the subfield 952$d, now it works fine. But it's a very important field for generating reports and keep tracks of books, we can not ignore this field.
Comment 3 Mengu Yazicioglu 2022-05-09 10:14:27 UTC
Hi,

See the bug 30717, this could be same
Comment 4 Jonathan Druart 2022-05-31 09:42:28 UTC

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