It is fixable. I’ve dealt with similar transformation issues in the past (with
a rather different cause). You can’t use iconv to do the conversion of what
the web server outputs, as there are a few bytes that show up that aren’t
considered to be valid cp1252 code points. We’ll see if the bit
On Thu, Dec 02, 2021 at 09:11:38AM -0500, Stewart C. Russell via talk wrote:
> I haven't had a chance to try them yet, but your note about the
> transformation being reversible gives me hope that it can be fixed.
Here is someone that hit problems latin1 vs utf8 encoding for wordpress
this year
On 2021-12-01 21:53, Jamon Camisso via talk wrote:
Do any of the casting suggestions on that link that I sent fix it?
I haven't had a chance to try them yet, but your note about the
transformation being reversible gives me hope that it can be fixed.
thanks,
Stewart
---
Post to this
On 01/12/2021 08:05, Stewart C. Russell via talk wrote:
On 2021-11-29 16:25, Jamon Camisso via talk wrote:
Another thing to try is using mysqli_set_charset("UTF8"); somewhere in
your site's code. Substitute in different character sets until you
find the correct one ...
Thanks, Jamon, but
On 2021-11-29 16:25, Jamon Camisso via talk wrote:
Another thing to try is using mysqli_set_charset("UTF8"); somewhere in
your site's code. Substitute in different character sets until you find
the correct one ...
Thanks, Jamon, but there isn't a valid encoding for what my database
seems
On 27/11/2021 14:41, Stewart C. Russell via talk wrote:
I have been running a WordPress blog hosted on a Linux-based shared host
since WordPress became a thing. It has worked quite well from about 2004
up until a few weeks ago.
So the phonetic character U+0252 has been mangled into U+00C9 +
On 27/11/2021 14:41, Stewart C. Russell via talk wrote:
I have been running a WordPress blog hosted on a Linux-based shared host
since WordPress became a thing. It has worked quite well from about 2004
up until a few weeks ago.
So the phonetic character U+0252 has been mangled into U+00C9 +
WordPress updates the database when it upgrades, so it entirely possible
that the database is profoundly changed by an upgrade.
I dump my WordPress database daily and back it up (I also use rsync to keep
an updated collection of media (mostly photos) in the wp-content folder,
because I hate
| From: Stewart C. Russell via talk
| On 2021-11-27 18:04, D. Hugh Redelmeier wrote:
| >
| > Do you have shell access? I think you imply "yes".
|
| Yes, I do, but not to the database server. All I have for that is socket
| access and PHPMyAdmin (blecch).
Ahh. Kind of "no".
| > Does "fix
On 2021-11-27 18:04, D. Hugh Redelmeier wrote:
Do you have shell access? I think you imply "yes".
Yes, I do, but not to the database server. All I have for that is socket
access and PHPMyAdmin (blecch).
Does "fix it" mean "changed the raw data" or mangle the data somewhere
downstream of
| From: Stewart C. Russell via talk
| I have been running a WordPress blog hosted on a Linux-based shared host since
| WordPress became a thing. It has worked quite well from about 2004 up until a
| few weeks ago.
Do you have shell access? I think you imply "yes".
| Sadly, *something*
I have been running a WordPress blog hosted on a Linux-based shared host
since WordPress became a thing. It has worked quite well from about 2004
up until a few weeks ago.
Sadly, *something* recently decided my database encoding was wrong. And
that something decided to "fix" it. It certainly
12 matches
Mail list logo
