From 61b666a17bcafee0224a558f9e60c266cfb34649 Mon Sep 17 00:00:00 2001 From: Matt Blenkinsop Date: Tue, 21 Oct 2025 11:26:09 +0100 Subject: [PATCH] Bug 41063: Fix additional fields in Vue Additional fields added through Vue.js resource forms were not being saved to the database. This was caused by using ref() instead of reactive() for the current_additional_fields_values object. Since ref() only provides shallow reactivity for objects, changes to nested properties were not being tracked properly. This switches to reactive() which provides deep reactivity tracking, ensuring that all changes to additional field values are properly captured and submitted when the form is saved. Test plan: 1) Go to Administration > Additional fields and add an additional field for erm_agreements 2) Enable ERM and navigate to ERM > Agreements 3) Click to add a new agreement and then fill out the form, making sure to add something into your new additional field 4) Hit save and navigate to the agreement you have just added 5) There will be no additional field added 6) Apply patch and yarn js:build 7) Repeat steps 3 - 5 8) The additional field should be added and displayed correctly Signed-off-by: David Nind Signed-off-by: Martin Renvoize --- .../prog/js/vue/components/AdditionalFieldsEntry.vue | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/koha-tmpl/intranet-tmpl/prog/js/vue/components/AdditionalFieldsEntry.vue b/koha-tmpl/intranet-tmpl/prog/js/vue/components/AdditionalFieldsEntry.vue index 5f77d405e28..e7d3dcc2636 100644 --- a/koha-tmpl/intranet-tmpl/prog/js/vue/components/AdditionalFieldsEntry.vue +++ b/koha-tmpl/intranet-tmpl/prog/js/vue/components/AdditionalFieldsEntry.vue @@ -125,7 +125,7 @@