Skip Navigation

Home › Support › English Support › [Closed] You are about to change the language of

[Closed] You are about to change the language of

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.

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

Supporter timezone: Europe/Zagreb (GMT+02:00)

Tagged: 

This topic contains 12 replies, has 2 voices.

Last updated by Bruno Kos 12 months ago.

Assisted by: Bruno Kos.

Author Posts
April 26, 2024 at 10:01 am

steveS-5

You are about to change the language of

April 26, 2024 at 10:30 am
April 29, 2024 at 8:50 am #15575631

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

It seems that some custom logic might be interfering, possibly modifying the language request or activating the JavaScript responsible for the dialogue. Can you please try the following:

1. Set up a minimal environment using the default theme.
2. Activate only the WPML core plugin to see if the issue persists.
May 1, 2024 at 4:03 pm #15584465

steveS-5

Dear Bruno,

I managed to get rid of the warning by figuring out which plugin was causing it.

However the pages still do not translate on the front end, and also when a change is made to the English version, the new text does not show up in the column for the English content of the translator page, it still shows the original text that was there at first.

Could you please check the about page and advise?
May 2, 2024 at 6:46 am #15585670

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

I see, the the issue would be on the page such as hidden link where it shows English even though it is translated to Spanish?

Can you do this?

1. Edit wp-config.php and insert the following lines (just before /* That's all, stop editing! Happy publishing. */ part)

define( 'WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true);
define( 'WP_DEBUG_DISPLAY', false);

2. Reproduce the issue - just open hidden link, open its translation and resave the translation.

3. Locate the debug log in: /wp-content/debug.log

4. Paste the latest lines here. No need to paste the entire log file, just 20 lines or so will do. Please censor any sensitive information.
May 2, 2024 at 5:07 pm #15588598

steveS-5

Thank you Bruno.

Yes correct that is the page.

Please find the debug log below, there were actually only 20 lines in the file, so it's the full file:

[02-May-2024 17:03:54 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:03:54 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
[02-May-2024 17:03:54 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:03:54 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
[02-May-2024 17:04:15 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:04:15 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
[02-May-2024 17:04:15 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:04:15 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
[02-May-2024 17:04:16 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:04:16 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
[02-May-2024 17:04:16 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:04:16 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
[02-May-2024 17:04:34 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:04:34 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
[02-May-2024 17:04:34 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:04:34 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
[02-May-2024 17:04:58 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:04:58 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
[02-May-2024 17:04:58 UTC] PHP Notice: Undefined index: center_status in /wp-content/plugins/floens-addon/common/functions.php on line 271
[02-May-2024 17:04:58 UTC] PHP Notice: Undefined index: url_hash_listner in /wp-content/plugins/floens-addon/common/functions.php on line 272
May 3, 2024 at 7:11 am #15589618

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

To troubleshoot this problem, I'll install the Duplicator plugin and generate packages for further debugging purposes. I'll ensure to exclude all media files to maintain a minimal package size. You can find more information about the process here: [link](https://wpml.org/faq/provide-supporters-copy-site/). Please confirm if this approach is acceptable to you.
May 3, 2024 at 7:31 am #15589651

steveS-5

Dear Bruno,

Yes please go ahead and proceed.
May 3, 2024 at 12:20 pm #15591333

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

I am checking this with our 2nd tier and will keep you posted.
May 6, 2024 at 10:48 am #15596683

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

I did a test on hidden link and it seems to be working.

Even if I added a new Elementor default element to non-working page (hidden link) that element translation also works.

Can you confirm that the translation doesn't show only for these custom Elementor widgets?
May 6, 2024 at 4:04 pm #15598677

steveS-5

Hi Bruno,

Yes it affects the custom elementor widgets that are already on the page, if I add a standard Elementor heading it will translate and register in the translation section.

When I update the newly added standard element heading the update shows on the translation page correctly and shows the Spanish translation highlighted in orange, this however does not happen on the custom elementor widgets, eventhough they have been registered.

Changes to the original version of the custom elementor widgets do not show in the translations, meaning when translating the original text is still showing in "original English" when in fact it has been changed. The translations are not showing on the front end either despite being translated, it just shows the "original English" text.

Kind regards,

Steve
May 7, 2024 at 10:33 am #15601176

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

We found the issue being with XML - we don't need to translate all the elements so XML should be:

<wpml-config>
  <elementor-widgets>
    <widget name="heading">
      <fields>
        <field>title</field>
      </fields>
    </widget>
    <widget name="floens-about">
      <fields>
        <field>sec_title</field>
        <field>sec_sub_title</field>
        <field>summary</field>
        <field>highlighted_text</field>
        <field>layout_one_progressbar_title</field>
        <field>button_label</field>
        <field>layout_two_sec_title</field>
        <field>layout_two_sec_sub_title</field>
        <field>layout_two_summary</field>
        <field>layout_two_highlighted_text</field>
        <field>layout_two_button_label</field>
        <field>layout_two_experience_year</field>
        <field>layout_two_experience_title</field>
        <field>layout_three_sec_title</field>
        <field>layout_three_sec_sub_title</field>
        <field>layout_three_summary</field>
        <field>layout_three_client_content</field>
        <field>layout_three_button_label</field>
        <field>layout_four_sec_title</field>
        <field>layout_four_sec_sub_title</field>
        <field>layout_four_summary</field>
        <field>layout_four_highligted_text</field>
        <field>layout_four_rounded_text</field>
        <field>layout_four_button_label</field>
        <field>layout_four_button_url>url</field>
      </fields>
      <fields-in-item items_of="layout_two_check_list">
        <field>title_one</field>
        <field>title_two</field>
      </fields-in-item>
      <fields-in-item items_of="layout_four_check_list">
        <field>title</field>
        <field>subtitle</field>
      </fields-in-item>
    </widget>
    <widget name="floens-process">
      <fields>
        <field>sec_title</field>
        <field>sec_sub_title</field>
      </fields>
      <fields-in-item items_of="process_list">
        <field>title</field>
        <field>subtitle</field>
      </fields-in-item>
    </widget>
    <widget name="floens-reliable">
      <fields>
        <field>sec_title</field>
        <field>sec_sub_title</field>
        <field>sec_summary</field>
        <field>layout_one_button_label</field>
        <field>layout_one_experience_yr</field>
        <field>layout_one_experience_title</field>
        <field>layout_two_sec_title</field>
        <field>layout_two_sec_sub_title</field>
        <field>layout_two_sec_summary</field>
        <field>layout_two_funfact_title</field>
        <field>layout_two_funfact_number</field>
        <field>layout_two_client_title</field>
        <field>layout_two_experience_yr</field>
        <field>layout_two_experience_title</field>
      </fields>
    </widget>
    <widget name="floens-team">
      <fields>
        <field>sec_title</field>
        <field>sec_sub_title</field>
        <field>sec_summary</field>
        <field>layout_two_sec_title</field>
        <field>layout_two_sec_sub_title</field>
        <field>layout_two_sec_summary</field>
        <field>layout_three_name</field>
        <field>layout_three_designation</field>
        <field>layout_three_summary</field>
      </fields>
      <fields-in-item items_of="team_items">
        <field>name</field>
        <field>designation</field>
        <field editor_type="LINK" key_of="url">url</field>
        <field>social_network</field>
      </fields-in-item>
    </widget>
    <widget name="floens-testimonials">
      <fields>
        <field>sec_title</field>
        <field>sec_sub_title</field>
        <field>layout_two_sec_title</field>
        <field>layout_two_sec_sub_title</field>
        <field>layout_three_sec_title</field>
        <field>layout_three_sec_sub_title</field>
      </fields>
      <fields-in-item items_of="layout_two_testimonials">
        <field>name</field>
        <field>designation</field>
        <field>testimonial</field>
      </fields-in-item>
    </widget>
  </elementor-widgets>
</wpml-config>

It seems to work now hidden link

Can you check?
May 7, 2024 at 8:49 pm #15603892

steveS-5

Dear Bruno,

I checked and it seems to work on the about page.

However when I try it on the home page I get the same problem again, the footer and header seem to translate.

I just copy the full XML and add that in the settings page of WPML and delete the parts that give an error. What am I doing wrong? as I will have to do this for every single page inorder for the site to work.

Kind regards,

Steve
May 8, 2024 at 8:16 am #15604788

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+02:00)

Does the home page or footer/header use the same elements?

If so, can you resave original pages (and make some minor change there) so that new XML takes effect, and then open the translation editor and resave?

If using some different XML, then you need to remove (from this XML) everything that makes no sense to be translated, such as element type, size, margins, etc.

The topic ‘[Closed] You are about to change the language of’ is closed to new replies.