Encoding Problem

[beck]

Hi,

after upgrading from 3.2.1.2 to 3.3.0.7 we are seeing massive problems. Site is ojs.uni-passau.de
Especially the encoding (site is in german) ist not working. DB is UTF-8 and the content is stored correctly (with umlaut).
DB upgrade ran.
My config looks like this:

;;;;;;;;;;;;;;;;;;;;;;;;;
; Localization Settings ;
;;;;;;;;;;;;;;;;;;;;;;;;;

[i18n]

; Default locale
locale = de_DE

; Client output/input character set
client_charset = utf-8

; Database connection character set
; Must be set to “Off” if not supported by the database server
; If enabled, must be the same character set as “client_charset”
; (although the actual name may differ slightly depending on the server)
connection_charset = UTF8

; Database storage character set
; Must be set to “Off” if not supported by the database server
database_charset = Off

; Enable character normalization to utf-8 (recommended)
; If disabled, strings will be passed through in their native encoding
; Note that client_charset and database collation must be set
; to “utf-8” for this to work, as characters are stored in utf-8
charset_normalization = utf-8

What can I do?

[beck]

After being directed to this forum by the support but getting no help at all - not even a response - I fixed it myself.
It does not speak of quality if the only response to my direct request was a try to sell a very expensive abo for a support flatrate.

Issue can be closed.

[asmecher]

Hi @beck,

It’s not unusual for a post here to go a few days without a response; PKP staff who help out on the forum are divided quite thin, and the community doesn’t get to every post. It sounds like you’ve solved the problem, though; could you document the solution to help build the knowledge base for anyone else encountering the same problem?

Thanks,
Alec Smecher
Public Knowledge Project Team