Activating WPML Multilingual CMS plugin causes Toolset debug info to be empty

This support ticket is created hace 1 año, 8 meses. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Asia/Karachi (GMT+05:00)

Este tema contiene 3 respuestas, tiene 3 mensajes.

Última actualización por Waqar hace 1 año, 8 meses.

Asistido por: Waqar.

Autor

Mensajes

septiembre 20, 2023 at 9:25 am #2645591

simonM-5

Hi Support

We are facing the issue again that Toolset Debug info is empty when certain plugins are activated. The last time we had this the WordFence plugin was the culprit. This time round it appears to be the WPML Multilingual CMS plugin. When it is activated the Toolset Debug Info become empty.

I've seen a few other users had similar issues due to the use of some Umlaut characters in the German language (Ä, ä, Ö, ö, Ü, ü). Our site is in English and German.

septiembre 20, 2023 at 3:34 pm #2645707

Nigel

Colaborador

Idiomas: Inglés (English ) Español (Español )

Zona horaria: Europe/London (GMT+01:00)

Hi Simon

I wasn't able to reproduce this, even though I added German to my site and created a post type using Umlauts in its name and translated some content and added lots of Umlauts to the content and taxonomy translations.

Are you able to isolate the cause any further? Do any of your plugins or your theme use Umlauts in their names, for example?

Does the problem occur if you only have Types and WPML active?

septiembre 21, 2023 at 9:05 pm #2646317

simonM-5

HI Nigel

I played around a little and activated the plugins one by one again. Now it works fine with WPML but not with WordFence again. I think WordFence could be blocking some kind of request. The last time we had this problem on our last ticket, WordFence was the culprit, but as in my original ticket it was WPML this time that was not playing ball.

I'm not sure why WPML is now working but WordFence not again. What is happening when we go to Toolset > Settings > Debug ?

Kind regards
Simon

septiembre 22, 2023 at 12:36 pm #2646531

Waqar

Hi Simon,

Thank you for sharing this update.

I couldn't reproduce this issue on my test website with WordFence activated. We also haven't received a similar report from any other user.

WordFence can restrict or block certain requests at times, as false positives.
( ref: enlace oculto )

You can get in touch with their support team if adjusting its settings doesn't work.

regards,
Waqar