From c0ea743def76cb3b911b4dad204a854d1ae40f6b Mon Sep 17 00:00:00 2001 From: Petro Vashchuk Date: Thu, 2 Jun 2022 14:47:39 +0300 Subject: [PATCH] Bug 29963: don't use set_to_today function at dateaccessioned.pl Don't use set_to_today function that was causing inconveniences when user was trying to edit items in batch, it would constantly set Date Acquired field to today's date which created the need for user to constantly manually clear the field, so that it doesn't overwrite the original Acquired date. When you add item without specifying any date for Date Acquired it automatically sets the today's date for it so this change doesn't seem to break any logic there. And when you try to edit item with already set Date Acquired before it will show the previously defined date, not disrupting anything here as well. To reproduce: 1. Edit items in batch for any biblio, see that "d - Date acquired" field is automatically set to current day's date. 2. Apply the patch 3. "d - Date acquired" should be empty after that. 4. Additionally, go to the additem.pl to edit single item and check that it correctly shows Date acquired in that field. --- cataloguing/value_builder/dateaccessioned.pl | 2 -- 1 file changed, 2 deletions(-) diff --git a/cataloguing/value_builder/dateaccessioned.pl b/cataloguing/value_builder/dateaccessioned.pl index 2f027c8e9a..d1377a2bf6 100755 --- a/cataloguing/value_builder/dateaccessioned.pl +++ b/cataloguing/value_builder/dateaccessioned.pl @@ -41,8 +41,6 @@ my $builder = sub { altInputClass: "input_marceditor flatpickr-input", dateFormat: "Y-m-d" }); - /* Set current date on page load */ - set_to_today($function_name.id); }); function Focus$function_name(event) { -- 2.28.0