Updated Debian to Stretch and now s9y delivers double-UTF8
Posted: Wed Aug 02, 2017 3:46 pm
Hi,
my blog is running with s9y since 2005 (or so), and I recently updated the system it runs on from Debian jessie to Debian stretch. The machine now has PHP 7.0, apache 2.4.25 and MariaDB 10.1. I think that the old system had php 5.someting, apache 2.4.10 and MariaDB 10.0.
s9y itself is running from a (admittedly outdated) git checkout of serendipity 2.0.5 from https://github.com/s9y/Serendipity.git.
Doing the system update broke my Umlauts. It looks like the Umlauts are displayed in UTF-8 after doing an additional and superfluous second conversion to UTF-8: The web page delivered is declared as
Note the broken Umlaut in "Verbunden über IPv6" in the sidebar, which confuses me because usually those encoding foo issues happen only with the actual _content_.
The database collation is utf8_unicode_ci: The blog itself is also set to UTF-8: Notice that in this screenshot, the actual Blog Title is already broken. I am pretty sure that it was correct before the OS upgrade.
On Twitter, @supergarv told me to twiddle with $serendipity{'dbNames'}, but from the changelog (docs/NEWS_OLD) this looks like it was only an experimental option and the frontend option "Enable DB Charset Conversion" has superseded that? I have tried both ways, with no result (no attachment, only 3 allowed).
Where am I supposed to set $serendipity{'dbNames'}? serendipity_config_local.inc.php seems to be overwritten from the frontend.
What am I supposed to restart after doing such a change? Is it only necessary to do Shift-Reload in the Browser?
Please note that I didn't do any database conversion or migration, it was just a minor version number upgrade from MariaDB 10.0 to MariaDB 10.1 (the big MySQL to MariaDB migration was half a year ago and didn't break things).
Any ideas? Thanks in advance.
Greetings
Marc
my blog is running with s9y since 2005 (or so), and I recently updated the system it runs on from Debian jessie to Debian stretch. The machine now has PHP 7.0, apache 2.4.25 and MariaDB 10.1. I think that the old system had php 5.someting, apache 2.4.10 and MariaDB 10.0.
s9y itself is running from a (admittedly outdated) git checkout of serendipity 2.0.5 from https://github.com/s9y/Serendipity.git.
Doing the system update broke my Umlauts. It looks like the Umlauts are displayed in UTF-8 after doing an additional and superfluous second conversion to UTF-8: The web page delivered is declared as
Code: Select all
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
The database collation is utf8_unicode_ci: The blog itself is also set to UTF-8: Notice that in this screenshot, the actual Blog Title is already broken. I am pretty sure that it was correct before the OS upgrade.
On Twitter, @supergarv told me to twiddle with $serendipity{'dbNames'}, but from the changelog (docs/NEWS_OLD) this looks like it was only an experimental option and the frontend option "Enable DB Charset Conversion" has superseded that? I have tried both ways, with no result (no attachment, only 3 allowed).
Where am I supposed to set $serendipity{'dbNames'}? serendipity_config_local.inc.php seems to be overwritten from the frontend.
What am I supposed to restart after doing such a change? Is it only necessary to do Shift-Reload in the Browser?
Please note that I didn't do any database conversion or migration, it was just a minor version number upgrade from MariaDB 10.0 to MariaDB 10.1 (the big MySQL to MariaDB migration was half a year ago and didn't break things).
Any ideas? Thanks in advance.
Greetings
Marc