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 | 14:00 – 18:00 | 13:00 – 18:00 | - |
Supporter timezone: America/Jamaica (GMT-05:00)
This topic contains 19 replies, has 3 voices.
Last updated by 2 years, 5 months ago.
Assisted by: Shane.
Hello,
Not sure i'm understanding fully here.
In your first statement your said "You're right. It comes from WPML. When I deactivate WPML, the problem is solved.
But I need that plugin for string translations."
Here you're stating that once WPML is disabled then the issue is no longer present .
Now you're stating below.
First, I don't use WPML for a multilingual website, so I use no strings at all for the homepage.
I also updated WPML Multilingual CMS to the latest version.
Second, When I deactivate String translation plugin, the problem stell remains.
Which gives me the impression that you're not using WPML, however the site is using WPML
When I checked the page again today I can see that the conditionals are now working. See Screenshot.
The article on the right is now displaying the taxonomy.
Thanks,
Shane
