Bug 38631 - Item search gives invalid JSON if a title has special characters
Summary: Item search gives invalid JSON if a title has special characters
Status: RESOLVED DUPLICATE of bug 37998
Alias: None
Product: Koha
Classification: Unclassified
Component: Searching (show other bugs)
Version: 24.05
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-05 12:48 UTC by Johanna Räisä
Modified: 2024-12-18 12:27 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johanna Räisä 2024-12-05 12:48:48 UTC
If the record title has a backslash the item search doesn't give results. We have few records which has a backslash in the title and it doesn't get escaped properly.
Comment 1 Katrin Fischer 2024-12-05 12:50:15 UTC
I wonder if this is a regression. I remember we had problems with a backslash title in the early days of item search.
Comment 2 Johanna Räisä 2024-12-05 12:59:53 UTC
Was it before 24.11? We have 24.05 version so I was wondering if there is a patch about it.

I will change the version for this one.
Comment 3 Katrin Fischer 2024-12-05 13:02:32 UTC
(In reply to Johanna Räisä from comment #2)
> Was it before 24.11? We have 24.05 version so I was wondering if there is a
> patch about it.
> 
> I will change the version for this one.

Way before. When the item search first was introduced :( 

I checked our ticket system, but unfortunately I didn't find it. I remember us checking if it was a false catalog record, but it turned out that the title indeed included the backslash correctly.
Comment 4 Katrin Fischer 2024-12-09 08:59:02 UTC
Hi Johanna, bug 37998 might be a duplicate or at least closely related.
Comment 5 Johanna Räisä 2024-12-10 07:25:29 UTC

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