Summary: | Editing date/datetime fields without the dateaccessioned.pl plugin can cause errors | ||
---|---|---|---|
Product: | Koha | Reporter: | Lucas Gass (lukeg) <lucas> |
Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | m.de.rooy |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31212 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Attachments: | Bug 32168: Add dateaccessioned.pl to 952 (datelastseen) for new installs |
Description
Lucas Gass (lukeg)
2022-11-10 16:08:17 UTC
It looks like we already added dateaccessioned.pl to $w, so we could probably also add it to datelastseen? Just wondering, if that could cause problems with bug 31212 925 - tagfield: "952" 926 tagsubfield: "w" 927 liblibrarian: "Price effective from" 928 libopac: "Price effective from" 929 repeatable: 0 930 mandatory: 0 931 kohafield: items.replacementpricedate 932 tab: 10 933 authorised_value: "" 934 authtypecode: "" 935 value_builder: dateaccessioned.pl 936 isurl: 0 937 hidden: 0 938 frameworkcode: "" 939 seealso: "" 940 link: "" 941 defaultvalue: Created attachment 146373 [details] [review] Bug 32168: Add dateaccessioned.pl to 952 (datelastseen) for new installs > Just wondering, if that could cause problems with bug 31212
Yes, I am running into this problem while working on 31212.
My patch enables dateaccessioned.pl by default with 952$r but should we also do the same for other date fields? |