Fix for #2427: added search term encoding & escaping to match the for…

…mat of the content in `bolt_field_translation`.

src/Repository/ContentRepository.php

@@ -98,11 +98,15 @@ public function searchNaive(string $searchTerm, int $page, int $amountPerPage, C
         $connection = $qb->getEntityManager()->getConnection();
         [$where] = JsonHelper::wrapJsonFunction('t.value', $searchTerm, $connection);
 
+        // The search term must match the format of the content in the database
+        // Therefore, it is JSON encoded and escaped with backslashes
+        $encodedSearchTerm = addslashes(trim(json_encode($searchTerm), '"'));
+
         $qb->addSelect('f')
             ->innerJoin('content.fields', 'f')
             ->innerJoin('f.translations', 't')
             ->andWhere($qb->expr()->like($where, ':search'))
-            ->setParameter('search', '%' . $searchTerm . '%');
+            ->setParameter('search', '%' . $encodedSearchTerm . '%');
 
         // These are the ID's of content we need.
         $ids = array_column($qb->getQuery()->getArrayResult(), 'id');