From 5f45818cf795d5456b0498269b33ed7d09e59dd7 Mon Sep 17 00:00:00 2001
From: Baptiste Wojtkowski <bski@laposte.net>
Date: Fri, 9 Aug 2024 16:33:37 +0200
Subject: [PATCH] Bug 37606: Fix framework export module to escape double
 quotes

When exporting a framework as csv, the exporter does not check the presence of double quote in the fields. Hence, if there is one double quote, the csv is broken.

TEST PLAN:
1 - Change a framework to add a field containing double quote in name
2 - Export it in csv
3 - Create a new framework
4 - Import the csv in the new framework -> every fields after the one
containing double quotes should be broke. Every other fields should have
no subfield
5 - APPLY PATCH
6 - Repeat 2-5 -> everything should be correctly exported

Signed-off-by: Sukhmandeep Benipal <sukhmandeep.benipal@inLibro.com>
Signed-off-by: Chris Cormack <chris@bigballofwax.co.nz>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
---
 C4/ImportExportFramework.pm | 1 +
 1 file changed, 1 insertion(+)

diff --git a/C4/ImportExportFramework.pm b/C4/ImportExportFramework.pm
index 3d44d46ec3..16295d61ab 100644
--- a/C4/ImportExportFramework.pm
+++ b/C4/ImportExportFramework.pm
@@ -291,6 +291,7 @@ sub _export_table_csv
             for my $field (@fields) {
                 my $value = $hashRef->{$field} // q||;
                 $value =~ s/[\r\n]//g;
+                $value =~ s/"/""/g;
                 $$strCSV .= '"' . $value . '",';
             }
             chop $$strCSV;
-- 
2.39.5