[Waiting for user feedback] bridge qode f shortcodes are not translatable?

Thank you for the access details!

The site has Dutch as it's default language.

Based on that the translations should happen from Dutch to English and not the other way, this practice will ensure everything works well and avoids any issues down the road.

That being said your homepage is created in English first and then translated to Dutch which is not ideal.

With that in mind I will proceed the way it is and resolve the issue of the shortcode not showing in the editor as it should show regardless which language you are working on.

------------------------

To resolve the issue of the Elements coming from Qode showing up in the ATE I registered them using a custom xml configuration code.

1. Go to WPML->Settings
2. Custom XML Configuration (tab at the top)
3. Added the following code
4. Make a small edit to the default language of the page and update
5. Update the translation.

<?xml version="1.0"?>
<wpml-config>

    <!-- Elementor widgets from Qode/Brok core -->

    <elementor-widgets>

        <!-- brok_core_section_title -->
        <!-- Used for titles like "Get ahead with Bamboo", "Applications", etc. -->
        <widget name="brok_core_section_title">
            <fields>
                <!-- Main heading -->
                <field type="Section title" editor_type="LINE">title</field>

                <!-- Body text below the title -->
                <field type="Section text" editor_type="AREA">text</field>
            </fields>
        </widget>

        <!-- brok_core_button -->
        <!-- Your "Contact us" CTA button -->
        <widget name="brok_core_button">
            <fields>
                <!-- Visible button label -->
                <field type="Button text" editor_type="LINE">text</field>

                <!-- Button URL; usually copied, but exposing it lets you localize URLs if needed -->
                <field type="Button link" editor_type="LINK">link</field>
            </fields>
        </widget>

        <!-- qi_addons_for_elementor_clients_slider -->
        <!-- Repeater with multiple "client" items in a slider -->
        <widget name="qi_addons_for_elementor_clients_slider">
            <fields>
                <!-- Title per slide (repeater) -->
                <!-- 'children' is the repeater name, 'client_title' is the field -->
                <field type="Client title" editor_type="LINE">children::client_title</field>
            </fields>
        </widget>

    </elementor-widgets>

    <!-- Slider Revolution -->
    <!-- The 'slider_revolution' widget here only stores the [rev_slider] shortcode.
         Translation should be handled on the Slider Revolution side with WPML,
         so no additional ATE config is strictly necessary. -->

</wpml-config>

Related Documentation:
https://wpml.org/documentation/support/language-configuration-files/

NOTE: I have performed the above already all you have to do now is access the ATE Editor and finish the translation 🙂

Let me know your results, please.

It’s fine that the default language was switched. Ideally, though, translations should always be created from the default language to the secondary language. If that’s not possible, just ensure you keep the workflow consistent.

Regarding your question:

“If we replace a PDF on the English site, will it update on the Dutch site?”

Updating the default language triggers an update for the translation, but it won’t sync automatically. The Dutch version will show the update icon (spinning circle), and you’ll need to open it to update the translation.

Please test this and let me know the results.

Glad to hear that!

"Can I assign the pages to the correct language?"

I'd recommend doing that if possible, you can edit the page and then on the drop down select the language that is appropriate so they are correctly indexed.

Hello,

Bobby is currently on vacation, so I will be taking care of your ticket in the meantime,

As explained before, editing a translation directly from your site editor will cause issues, I understand that you have changed the site language to Dutch, but this page : hidden link

Was originally created in English and then translated as shown here : hidden link

So here we have two different parameters :
- Default language : This is the first language displayed to site visitors when accessing your site
This was changed from English to Dutch
- Original language : This is the source language used in translations, each page is different, in this case, that page was created in English then Translated to Dutch, which makes its original language as "english"
We recommend to only edit the page in the original language then apply the changes to translation using translation editor

If you'd like to also change the original language of a page, it is possible by redoing the translation from Dutch to English (deleting the English page)

Or you can manually edit the page using this workflow :

1- Unlink the translation: https://wpml.org/fr/faq/how-to-disconnect-translations-from-the-default-language-page-or-post/

2- Edit the translation (Dutch) using your site's editor

3- Relink the translation: https://wpml.org/fr/faq/how-to-link-already-translated-pages/

However, this means that you cannot use WPML editor for this page, and that any subsequent changes will have to be made manually by you using the site editor.

I hope this is clear, let me know if you have any questions,

Hello,

Here is a video showing how to let WPML detect the undetected fields (benefits, size...) and what to do about the lost translation : hidden link

I can retranslate the page using automatic translation, then edit the English page and see if any of the translations is lost, let me know if I'm missing anything.

Hello,

I have completed the translation for both :
hidden link
hidden link

Please review the translation and see if everything is working as expected.

I followed the following workflow :

1- If the page has fields not detected by WPML, then simply edit the English (original language) page slightly (add a space or character to the content)
This will apply the XML code to detect those fields we registered
2- Open the translation editor
3- Retranslate any English parts or missing translations
4- Complete

PS: I have assigned 5000 credits to your site and used the automatic translation for those parts using this icon : hidden link

Best,