Skip Navigation

[Resolved] Toolset / WPML issue

This thread is resolved. Here is a description of the problem and solution.

Problem:

The content on the blog archive page is not fully translated. A slider added to the archive template appears correctly in the default language (Spanish), but in other languages (e.g., English), a different slider from another plugin is shown. The archive pages sometimes show French as the default language instead of Spanish, indicating a potential conflict between WPML and Toolset.

Solution:

The customer discovered that the plugin "Post Types Order" by Nsp Code was causing the issue. This plugin created different template versions for each language and changed the default language of existing templates.

Deactivating and reactivating plugins one by one helped identify the culprit.

The customer removed the "Post Types Order" plugin, which resolved the issue.

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 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Sao_Paulo (GMT-03:00)

This topic contains 15 replies, has 2 voices.

Last updated by Mateus Getulio 5 months ago.

Assisted by: Mateus Getulio.

Author
Posts
#2704751

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi,

We apologize for the delay with this, it turned out to be quite a complex case.

I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue and will try to find a solution.

I will get back to you as soon as I get an answer from them.

Best regards,
Mateus

#2704982

Hi,
I've found the problem.

There was a plugin, called "Post Types Order" by Nsp code, that was causing the issue.
And it has been difficult to find out, even deactivating and activating back all plugins one by one.

What this plugin does is create different a template version for each language (see here: hidden link), and even changing the default language of an existing template.

I have removed the plugin altogether, and now the problem is gone