[Escalated to 2nd Tier] Widget translation problem
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Elementor users - please update WPML to the latest version to maintain compatibility. More details here - https://wpml.org/changelog/2024/12/wpml-4-6-15-critical-update-for-elementor-sites/
After an update, I have found out that all my widgets had disappeared! So I have recreated them but I face some bugs. The widget translation language is randomly changed.
When I create a widget, I need to close all the others ones. Otherwise, language change on a widget will eventually not be saved in the right one.
Then, try this :
1/ create a widget
2/ add some text
3/ set it to a specific language (like french for instance)
4/ save
5/ reload the page
6/ you'll see that the language has been saved to all languages instead of french
Normally, you would need to translate your widgets with the WPML String Translation module.
If you don´t have this module installed, then we recommend that you use the "WPML Widgets" to translate your widgets.
The memory footprint of the String Translation Module is too high to justify an installation just for that purpose as it seems to be feasible without it. The issue is that the widget language isn't saved properly. There is a bug. Have you tried to reproduce this?
1. Replicate problem
I was unable to replicate the issue on my local server
On my test system (String Translation not installed) I did the following steps:
1. Created 2 new text widgets
2. Set the "Languages" for one to be "EN" (my defaut language)
Set the "Languages" for the second to be "ES" (my secondary language)
3. I added the 2 widgets to the footer of the theme
4. When I display the page in ES, the ES widget appears
When I display the page in EN, the EN widget appears
I have loaded pictures to demonstrate this.
2. Please note that only "Text" widgets can become multilingual with the core WPML CMS blog subscription.
3. FInally, there are no reported issues with Widgets at the moment in our internal database nor are there existing erratas.
Ok. Following the same steps in your screencast, I can replicate the scenario.
I also see that the language remains if you save the widget twice which implies some kind of initialisation of that field with the default value of "All Languages" when the widget is first added to the widget zone.
I will escalate this as a bug and with the known workaround to be the requirement of setting/saving the widget language 2xs.
