NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      Setting Confluence default encoding to UTF-16 renders 'chinese' characters for spaces and even the login screen.

      It is also impossible to set it back to UTF-8, since the UI is not rendered:

      To verify this is the problem run in the database:

      SELECT BANDANAVALUE FROM BANDANA where BANDANAKEY = 'atlassian.confluence.settings';
      

      if it returns a different value of UTF-8 in the result, then it is affected.

      Steps to reproduce:

      1. Set up a new Confluence
      2. Go under the Administrator Panel > General Configuration > Formatting and International Settings and change Encoding field from UTF-8 to UTF-16.

      Expected Result:
      Confluence doesn't allow the change
      Actual Result:
      Confluence becomes unusable, styles are broken and administration sections are locked.
      Can't be reverted back unless a DB change is done.

      Workaround

      1. Shut down Confluence and perform a database backup
      2. Run:
        UPDATE  BANDANA set BANDANAVALUE = REPLACE(BANDANAVALUE, 'UTF-16', 'UTF-8') where BANDANAKEY = 'atlassian.confluence.settings';
        
      3. Start Confluence

            [CONFSERVER-35907] Setting Confluence to use UTF-16 encoding causes problems

            Mauro Badii (Inactive) added a comment - Closing as duplicate of: https://jira.atlassian.com/browse/CONF-35275

            Quick workaround:

            UPDATE  BANDANA set BANDANAVALUE = REPLACE(BANDANAVALUE, 'UTF-16', 'UTF-8') where BANDANAKEY = 'atlassian.confluence.settings';
            

            Mauro Badii (Inactive) added a comment - Quick workaround: UPDATE BANDANA set BANDANAVALUE = REPLACE(BANDANAVALUE, 'UTF-16', 'UTF-8') where BANDANAKEY = 'atlassian.confluence.settings';

            We should either prevent users from changing encoding to UTF-16 or properly support this encoding type.

            Steve Haffenden (Inactive) added a comment - We should either prevent users from changing encoding to UTF-16 or properly support this encoding type.

              Unassigned Unassigned
              emallmann Eduardo Mallmann (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: