Skip Navigation

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/
Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 10:00 8:00 – 10:00 8:00 – 13:00 8:00 – 13:00 9:00 – 13:00 -
- 11:00 – 17:00 11:00 – 17:00 14:00 – 17:00 13:00 – 17:00 13:00 – 18:00 -

Supporter timezone: America/New_York (GMT-05:00)

Tagged: 

This topic contains 0 replies, has 0 voices.

Last updated by Lauren 1 day, 21 hours ago.

Assisted by: Lauren.

Author Posts
December 16, 2024 at 10:06 pm #16519016

barjD-2

Background of the issue:
I have strings in Custom HTML widgets which were translated, but not showing on the front end of the website.

I increased memory limit to 256M

I deleted existing strings under WPML > String Translation

I re-scanned the parent theme and child theme under WPML > Theme and plugins localization

I added translations for the strings again.

I cleared website cache and refreshed the front end of the website.

The issue can be seen at the bottom of this page: hidden link

Symptoms:
The translations are saved, but they still don't appear on the front end of the website, even after clearing cache and viewing in incognito mode. Deactivating all plugins except WPML plugins did not resolve the issue.

Questions:
Can you help us solve the translations not appearing on the front end of the website?

December 17, 2024 at 1:21 am #16519355

barjD-2

I have noticed that performing the following steps solves this issue:

Switch the theme to Twenty Twenty-One

Install the "Classic Widgets" plugin from the Plugins screen in WordPress

Navigate to Appearance > Widgets

Click, drag and drop the original widget from "Inactive Widgets" to the Footer widget area

Switch the theme back to the original (in our case, Genesis with child theme)

Navigate to Appearance > Widgets

Click, drag and drop the original widget from the widget area where it has been automatically assigned (in my case "Primary Sidebar"), to the position where it 'should' go (in our case, "Footer 3")

Navigate to WPML > String Translation

Find a new string with the Domain of "Widget" and the Name of "widget body" which has the same text shown in the Custom HTML widget string which does not show its translation on the front end of the website

Translate the string in the new, "widget body" field.

Wait for a message to confirm the translation is saved.

Refresh the front end of the website.

The translation appears.

Deactivate and unistall the Classic Widgets plugin (Genesis uses Classic Widgets without requiring this plugin)

Can someone let us know why it takes these steps for the translation to appear, instead of appearing automatically from the Custom HTML widget?

Or why the "widget body" string doesn't appear until we switch to Twenty Twenty-One theme?

I added a "test" widget with Custom HTML widget, navigated to WPML > String Translation

I added a translation to the 'test' Custom HTML widget. I refreshed the front end of the website, and the translation now appears. But why won't it show the translation for the previous Custom HTML widgets?

A screenshot is attached to show what is described above.

Screenshot 2024-12-16 at 5.10.39 PM.png
December 17, 2024 at 7:22 pm #16523267

Lauren
Supporter

Languages: English (English )

Timezone: America/New_York (GMT-05:00)

Please install a copy of your theme and your child theme on the test site that I set up, so that we can attempt to reproduce the issue there as well.

December 20, 2024 at 8:42 am #16532545

barjD-2

Hello, I just saw this message but will be away for the holidays. Can we please leave this ticket open until the first week of January? I will be able to install the theme at that time.

December 20, 2024 at 3:33 pm #16534782

Lauren
Supporter

Languages: English (English )

Timezone: America/New_York (GMT-05:00)

Sure, we will be happy to revisit the issue after the holidays.