Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-18202

German Umlauts break the QuickSearch

XMLWordPrintable

      The quick search breaks at the first non-ascii character.

      Steps to reproduce:

      • create a page named "Thöggele"
      • wait until it is indexed
      • try finding the page via quick search by entering "T" and "h" (everything is ok)
      • press "ö" (you will see that nothing changes on the UI, especially the ö in Thöggele is not bold), and the search is not narrowed

      Fix:

      • in the file (3.1, similar in 3.0)
        confluence-3.1-std/confluence/WEB-INF/classes/com/atlassian/confluence/setup/atlassian-bundled-plugins.zip, and inside there
        auiplugin-2.0.2.1.jar
      • patch the file
        js/atlassian/atlassian.js
        the function "escape" like this: 
          339,341c339
<                 return escape(string).replace(/%u\w{4}/gi, function (w) {
<                     return unescape(w);
<                 });
---
>                 return encodeURIComponent(string);
      • re-package the jar and zip and place it in the original file location, and restart confluence, and try again. It works now

        1. umlauts.jpg
          umlauts.jpg
          81 kB

            [CONFSERVER-18202] German Umlauts break the QuickSearch

            AndreasS added a comment -

            works fine for us

            AndreasS added a comment - works fine for us

            AndreasS added a comment -

            same issue for 3.1.1 and workaround (see above) works also fine

            AndreasS added a comment - same issue for 3.1.1 and workaround (see above) works also fine

            Andrew Lynch (Inactive) added a comment - - edited

            Actually I may be incorrect.
            I believe it may work correctly when UTF-8 is NOT specified.

            Andrew Lynch (Inactive) added a comment - - edited Actually I may be incorrect. I believe it may work correctly when UTF-8 is NOT specified.

            Andrew Lynch (Inactive) added a comment -

            Hi,

            Are you sure that you have propely configured Tomcat to use UTF-8 request URI encoding as described here?
            Quicksearch works fine for umlauts on my development environment (with URI encoding correctly set up).

            Regards,
            Andrew Lynch

            Andrew Lynch (Inactive) added a comment - Hi, Are you sure that you have propely configured Tomcat to use UTF-8 request URI encoding as described here ? Quicksearch works fine for umlauts on my development environment (with URI encoding correctly set up). Regards, Andrew Lynch

            Stephan Vollmer added a comment -

            An additional observation to this issue: When a page title has a german umlaut at position 1 or 2, then these pages are not shown in the live search result list. Normally, after typing the 2nd character, a list with matching pages appears. But in this case there are no results shown.

            Example page titles:

            • Übersicht – (umlaut at pos 1)
            • Häufig verwendete Befehle – (umlaut at pos 2)

            These words are quite common in german (in fact, these pages exist in our wiki).

            Stephan Vollmer added a comment - An additional observation to this issue: When a page title has a german umlaut at position 1 or 2, then these pages are not shown in the live search result list. Normally, after typing the 2nd character, a list with matching pages appears. But in this case there are no results shown. Example page titles: Übersicht – (umlaut at pos 1) Häufig verwendete Befehle – (umlaut at pos 2) These words are quite common in german (in fact, these pages exist in our wiki).

              xtjhin Joshua Tjhin (Inactive)
              da3888a75811 Gerhard Müller
              Affected customers:
              6 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: