Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#11 2019-01-01 19:23:44
- colak
- Admin
- From: Cyprus
- Registered: 2004-11-20
- Posts: 7,374
- Website
Re: Encoding problem
In reply to gaekwad #315873:
Looks like OP is already running 4.7.2:
The diagnostics image says 4.6.2
Yiannis
——————————
neme.org | hblack.net | LABS | State Machines | Respbublika! | NeMe @ github
Offline
#12 2019-01-01 19:39:22
- gaekwad
- Admin
- From: People's Republic of Cornwall
- Registered: 2005-11-19
- Posts: 2,633
Re: Encoding problem
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.
Offline
#13 2019-01-01 20:26:39
- Rob.
- New Member
- Registered: 2018-12-31
- Posts: 6
Re: Encoding problem
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
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
Offline
#14 2019-01-01 20:36:11
- Rob.
- New Member
- Registered: 2018-12-31
- Posts: 6
Re: Encoding problem
gaekwad wrote #315876:
The trailing
_ci
means character insensitive, which also mangles accented characters, if it was me I would try eitherutf8_bin
orutf8mb4_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?
Offline
#15 2019-01-01 20:42:46
- colak
- Admin
- From: Cyprus
- Registered: 2004-11-20
- Posts: 7,374
- Website
Re: Encoding problem
Did you try the htaccess way? you can add AddDefaultCharset utf-8
on the top of the file.
Yiannis
——————————
neme.org | hblack.net | LABS | State Machines | Respbublika! | NeMe @ github
Offline
#16 2019-01-01 21:26:27
- bici
- Member
- From: vancouver
- Registered: 2004-02-24
- Posts: 1,526
- Website
Re: Encoding problem
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.
…. texted postive
Offline
#17 2019-01-01 21:39:16
- Rob.
- New Member
- Registered: 2018-12-31
- Posts: 6
Re: Encoding problem
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.
Offline
#18 2019-01-02 18:11:55
- etc
- Developer
- Registered: 2010-11-11
- Posts: 3,414
- Website
Re: Encoding problem
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.
Offline
#19 2019-01-02 18:36:48
- gaekwad
- Admin
- From: People's Republic of Cornwall
- Registered: 2005-11-19
- Posts: 2,633
Re: Encoding problem
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)
Offline
#20 2019-01-02 20:13:58
- singaz
- Member
- Registered: 2017-03-12
- Posts: 75
Re: Encoding problem
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?
Sorry my horror English. I’m learning textpattern, I’m learning English
Offline