Pedro_md7

Appearently the issue is that it’s trying to insert an emoticon in the database, and it doesn’t seem to recognize that character.

The error is thrown when it finds \xF0\x9F\x98\x9C in a retweet (in hexadecimal, which seems to translate, applying the encoding to: ??).

You can see the original tweet in https://twitter.com/_CarlosRivera/status/467000934070243328

Is there any way to avoid that kind of emoticons, or replace them with a question mark or just remove them?

Thank you in advance.

Yes! it has finally solved the problem by replacing line 35 by:

$label = $tag_obj[‘prefix’] . mb_convert_encoding(strtolower($label), “UTF-8”);

Infinite thanks for the help, really.

Regards, Pedro.

Hello, we have tried to set the collation of both the field and the table and it doesn’t seem to work. What I’ve noticed is the following:
When I send the post from within the page, I can see that the client is sending the form data correctly, however, I don’t know what encoding it is using (see the parameter in the post below):

https://imageshack.com/a/img823/2325/d2k0.jpg

However, the SQL instruction is:

INSERT INTO wp_wp_rp_tags (post_id, post_date, label, weight)
VALUES (2778, ‘2014-02-17 13:36:46’, ‘P_amantes de teruel’, 10.000000), (2778, ‘2014-02-17 13:36:46’, ‘P_bodas de isabel de segura’, 10.000000), (2778, ‘2014-02-17 13:36:46’, ‘P_espa?±a’, 10.000000), (2778, ‘2014-02-17 13:36:46’, ‘P_teruel’, 10.000000), (2778, ‘2014-02-17 13:36:46’, ‘C_destacamos’, 5.000000), (2778, ‘2014-02-17 13:36:46’, ‘C_noticias’, 5.000000), (2778, ‘2014-02-17 13:36:46’, ‘C_reto de grupo europa’, 5.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_de’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_isabel’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_durant’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_lo’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_la’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_diego’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_san’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_semana’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_padr’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_iglesia’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_el’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_pedro’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_cinco’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_hoi’, 2.000000), (2778, ‘2014-02-17 13:36:46’, ‘A_don’, 2.000000);

In which it’s trying to insert ‘P_espa?±a’. It seems to be a problem in an encoding discrepancy between the encoding the server is expecting, and the encoding it’s receiving from the client. Is there a way we can make the server expect a different encoding, or to change the post encoding so the server receives the post correctly?

Best regards.

The value for DB_CHARSET in wp_config.php is set to utf8, however, the value for DB_COLLATE is set to an empty string (”). The collation for all the tables in the database is set to utf8_general_ci.

This seems to happen when making any posts with special characters such as accents or “?”.

It keeps crashing: https://blog.grupoeuropa.com/index.php/ronda-candidato-a-ser-patrimonio-de-la-humanidad.

Hello again, sorry it took so long to answer, is that I have no direct access to the database.

We executed the following line in the database and keeps crashing.

ALTER TABLE wp_wp_rp_tags DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

Thanks.

Thanks for the reply.

Okey, for example this post: https://blog.grupoeuropa.com/index.php/ronda-candidato-a-ser-patrimonio-de-la-humanidad/. Its tags is “Espa?a, Europa, Patrimonio de la Humanidad, Ronda”. In particular, the failure is given by the character ‘?’ of “Espa?a”.

However, the post works again refreshing the page, then check yourself.

Greetings and thanks for the help.

Vale ya he resuelto la duda, había que tocar el javascript. Por si a alguien le sirve de ayuda, es en esta línea: “this.init()}var m={show:{google:!0,linkedin:!0,facebook:!0,twitter:!0,reddit:!0,meneame:!0}“.

De derecha a izquierda, elegimos el orden que deseemos.

Saludos.