Skip to content Skip to sidebar

Home › Support › English Support › [Closed] bridge qode f shortcodes are not translatable?

[Closed] bridge qode f shortcodes are not translatable?

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
- 7:00 – 15:00 7:00 – 15:00 7:00 – 15:00 7:00 – 15:00 7:00 – 15:00 -
- - - - - - -

Supporter timezone: Pacific/Easter (GMT-06:00)

Tagged: , ,

This topic contains 20 replies, has 0 voices.

Last updated by Ilyes 4 months, 3 weeks ago.

Assisted by: Ilyes.

Author Posts
December 3, 2025 at 9:40 am #17629850

Peggy Vancorenland

This works perfect now. Thank you very much. Also big thanks for the credits, as I had to re translate quiet some pages.

But it looks like all pages are correct now:)

About the menu. On the frontend it works perfect. But in the backend I can only see the English menu now. Should we re translate this again as well? Or is it not necessary now that it works fine on frontend?

Thanks!

December 3, 2025 at 4:08 pm #17631629

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Bonjour,

WPML applique automatiquement la traduction des éléments de menu et les synchronise dans toutes les langues. Vous pouvez voir comment cela se synchronise ici : hidden link

Cela fonctionne comme prévu, sauf si vous souhaitez avoir manuellement des noms d'éléments et des URL différents dans d'autres langues, auquel cas vous pouvez les traduire manuellement à partir d'ici : hidden link
December 4, 2025 at 9:03 am #17633071

Peggy Vancorenland

Ok great!

One more; This page: hidden link
In the ATE everything is in Dutch and 100% translated, however in the front end it stays on English. The links do work correctly, they go (weirdly) enough to the Dutch corresponding urls. Even though they are not translated in the ATE.

Should I redo the page?

December 4, 2025 at 4:38 pm #17635426

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Hello,

Yes, it seems the same issue with this page too, first try changing the original page a bit (add a character or space to content), this will make WPML rescan the page again to see if any new fields are loaded.

Let me know if you want me to help you with it

December 4, 2025 at 7:10 pm #17636019

Peggy Vancorenland

Can you please have a look? I just added a space on the English page, but now the text on the Dutch page with ATE is missing. Tried it again, with rewriting a bit on the English page, but no change in the ATE.

Thank you.

December 4, 2025 at 10:35 pm #17636337

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

It turned out to be a another widget that should be registered in the XML, I added this to the existing XML code : 

        <widget name="brok_core_info_section">
      <fields>
        <field>title</field>
        <field>info_text</field>
        <field>text</field>
        <field>link</field>
      </fields>
    </widget>

It seems every widget of this theme is untranslatable, so each time you find a section not detected, we need to register it too.

I have translated the content, you need to edit the URLs in the translations yourself if that's okay.

The topic ‘[Closed] bridge qode f shortcodes are not translatable?’ is closed to new replies.