Encoding problem

colak · 2019-01-01 19:23:44

In reply to gaekwad #315873:

Looks like OP is already running 4.7.2:

The diagnostics image says 4.6.2

gaekwad · 2019-01-01 19:39:22

colak wrote #315875:

The diagnostics image says 4.6.2

Yes – different user – I’m guessing the image is from when the problem occurred for them. Both are running MariaDB 10.1.something which is MySQL 5.7.something (or near enough).

The trailing _ci means character insensitive, which also mangles accented characters, if it was me I would try either utf8_bin or utf8mb4_bin on a test server and see how that plays.

Rob. · 2019-01-01 20:26:39

singaz wrote #315869:

About 6 months ago

New hosting I fought for two weeks

I read the forum for two weeks

I found two posts

Message one

Second post

I fixed my problem

That’s my idea

Thank you Singaz. I have also found these posts, but I didn’t understand them. I don’t know which php file should I edit to patch this missing line (I couldn’t find txplib_db.php in TXP 4.7.2). Moreover for my case encoding was correct for TXP 4.6.2 and the problem appears after upgrading to 4.7.2 (also php from 5.6 to 7.2 – for both php versions problem is the same).
So if anyone have other suggestions – I still need help :( and I open to check new ideas.

Happy New Year for everyone

Rob. · 2019-01-01 20:36:11

gaekwad wrote #315876:

The trailing _ci means character insensitive, which also mangles accented characters, if it was me I would try either utf8_bin or utf8mb4_bin on a test server and see how that plays.

Could you explain it? What should I do? I guess that you write about hosting settings not TXP settings, don’t you? I have access to DirectAdmin and phpMyAdmin. How can I do a test that you mention?

colak · 2019-01-01 20:42:46

Did you try the htaccess way? you can add AddDefaultCharset utf-8 on the top of the file.

bici · 2019-01-01 21:26:27

colak wrote #315879:

Did you try the htaccess way? you can add AddDefaultCharset utf-8 on the top of the file.

Or is it possible to copy out the BB sql file, edit to add the “ AddDefaultCharset utf-8” in the sql directly. and then re-import that file.

BACKUP everything before trying.

Rob. · 2019-01-01 21:39:16

It seems to me that I solved the problem by accident :)
I have found the txplib_db.php in Lib directory and I have tested different settings “utf8_*” in line 223 and 225. Without any success. Then I decided to try to remove this block of code by commenting lines from 217 to 227. I have refreshed the page and now it’s work! I don’t know the explanation but I don’t care – I can continue to work with the blog.

Thank you for your assistance. “Encoding issue” can be mark as SOLVED and CLOSED.

etc · 2019-01-02 18:11:55

Thanks for the report. I’ve never seen this part of the code before, but it looks like it is MySQL 5 specific. In my Diagnostics db version reads as

MySQL: 5.5.5-10.1.37-MariaDB (mariadb.org binary distribution)

which seems to work fine. But in your case it is reported as

MySQL: 10.1.24-MariaDB-cll-lve (MariaDB Server)

so the version is possibly wrongly detected. Needs further testing.

gaekwad · 2019-01-02 18:36:48

Oleg – from memory, I’ve seen MariaDB-cll-lve appear on cPanel servers, if that helps research.

Last edited by gaekwad (2019-01-02 18:36:59)

singaz · 2019-01-02 20:13:58

Addition.

This is not a problem. The site works fine without errors.

But there is one incomprehensible line (see screenshot):

Initially the site worked on version 4.5.7. The site is constantly updated with the release of new versions of the engine (4.6.0, 4.6.1, 4.6.2 ….. 4.7.2)

I do not remember when the string appeared.

Checked base Notepad ++. There are no words in the database /etc pki /tls /certs /tmp /var /usr /local /php55 /lib /php

Where can these records be stored?

Textpattern CMS

Textpattern CMS support forum

#11 2019-01-01 19:23:44

Re: Encoding problem

In reply to gaekwad #315873:

#12 2019-01-01 19:39:22

Re: Encoding problem

colak wrote #315875:

#13 2019-01-01 20:26:39

Re: Encoding problem

singaz wrote #315869:

#14 2019-01-01 20:36:11

Re: Encoding problem

gaekwad wrote #315876:

#15 2019-01-01 20:42:46

Re: Encoding problem

#16 2019-01-01 21:26:27

Re: Encoding problem

colak wrote #315879:

#17 2019-01-01 21:39:16

Re: Encoding problem

#18 2019-01-02 18:11:55

Re: Encoding problem

#19 2019-01-02 18:36:48

Re: Encoding problem

#20 2019-01-02 20:13:58

Re: Encoding problem

Board footer