Support Forum
Support Forum
Offline
Ok got it! I know why the post gets corrupted, @yellow-swordfish was right: it's something in the content of the post itself!
I hardly use the mobile phone for the forum but 80% of my readers do. Ida told me "oh maybe the problem is because I put some emoticons". Well yes, it is... with the keyboard of the mobile is possible to add an endless number of emoticons and that is what caused the post's corruption. I tested myself.
But I cannot prevent people from entering emoticons, especially the ladies who follow my blog and the diet... 😀 😀 So what can be done about this?
My forum (in Italian) is: MsPforum
Offline
Oh... good catch. I really should have thought of that myself.
First thing we need to do is confirm version numbers. So - easiest way to go is to the forum admin > toolbox > environment and copy and paste the two top entries (Simple:Press and WordPress) for me to see please.
 |
YELLOW
SWORDFISH
|
Offline
Here you are:
| Simple:Press |
Version: 6.0 Build: 12969 Release: Development |
|
| WordPress |
Version: 4.2.2 Language: it-IT Character Set: UTF-8 Theme: Altervista Keith |
My forum (in Italian) is: MsPforum
Offline
Some background information. To support the entry of emoji's the database tables have had to be changed. WordPress support for emoji's happened in version 4.2.1 I believe. So you see all this is very recent. Simple:Press was built in on the last update. To enable the correct type of table is created we rely on a WordPress setting. I am wondering of this was set correctly in your system.
We may need to check that and it may take some time but I will work out the best way to do that today.
|
YELLOW
SWORDFISH
|
Offline
Ok, if you need any other info from me just ask. Infact if you tag me is better so I see how Mentions works 😀 I just uploaded it on my forum but have no idea of what happens if I get tagged!
My forum (in Italian) is: MsPforum
Offline
@matalena - you've been tagged!
I am a little worried about this. Would you be able to run a couple of small queries in phpMyAdmin so we can check your DB settings? I can give you step by step instructions...
|
YELLOW
SWORDFISH
|
Offline
Oh I see, I get a line at the top with the tag, great 😀
And as for the database queries, sure, I don't mind at all. I can get to the db and paste some Select if you write them here, no problem!
My forum (in Italian) is: MsPforum
Offline
There are two queries I would like you to try. What i would like you to do is copy the result and send it to me. I would suggest you do that via a private message so you do not publicly disclose your table prefix.
The two queries are:
SHOW CREATE TABLE xxx_posts;
SHOW CREATE TABLE xxx_sfposts
where 'xxx' needs to be your WordPress table prefix of course.
These can be run - one at a time - from the phpMyAdmin 'SQL' menu item at the top.
Depending on your version of phpMyAdmin - it might not show the entire result in the grid. But there should be an option underneath the result grid labelled 'print view with full texts'. if you click on that it will display a print version of the result which can be copied and then pasted back to us.
Is that OK?
|
YELLOW
SWORDFISH
|
Offline
Well. Not sure what is going on here. I am going to have to get techie for a moment and I apologise for that AND apologise if you know all this but I am assuming you do not.
Right up until 2 releases ago WordPress used utf-8 encoding for all of it's tables by default. With the advent of emojis and the need to support them in blog comments they decided to convert all table text columns from utf-8 to a character set of utf8mb4 (and collation of utf8mb4_unicode_ci). This change was performed in an upgrade script.
Our own database was upgraded this way - from a WP upgrade. I have just run a test on an older database I keep for testing, and the WP upgrade does indeed do this. I have also just installed a brand new WP 4.2.2 to ensure that a new WP created the correct table data. And yes it does.
But your tables have NOT been converted. WordPress itself is running the old encoding and returning the old encoding when queried. Because of this the SP tables did not get upgraded either.
But I have no idea why WordPress would fail to do this. Bit I will keep digging.
|
YELLOW
SWORDFISH
|
All RSS1 Guest(s)