Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

**Problem:** The client was experiencing issues with translating Kadence forms on their website. Despite making the forms and custom fields translatable, the 'send' button was missing, and the forms were not displaying correctly in different languages. The client suspected that the blocks were not registered in WPML and was unsure how to select the correct form in the Advanced Translation Editor (ATE).

**Solution:** We addressed the issue by incorporating a custom XML configuration to ensure that the Kadence blocks are recognized and translatable by WPML. Here is the XML configuration we used:

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="kadence/advanced-form-text" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-textarea" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-submit" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-telephone" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-email" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-file" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-select" translate="1">
      <key name="label"></key>
      <key name="helpText"></key>
      <key name="options">
        </key><key name="*"></key>
      
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form" translate="1">
      <key name="id">
      </key>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. We also highly recommend checking related known issues at [https://wpml.org/known-issues/](https://wpml.org/known-issues/), verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at [https://wpml.org/forums/forum/english-support/](https://wpml.org/forums/forum/english-support/).

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.

Tagged: 

This topic contains 11 replies, has 2 voices.

Last updated by Kor 1 month, 3 weeks ago.

Assisted by: Kor.

Author Posts
October 7, 2024 at 2:29 pm

Thomas

Background of the issue:
I have two Kadence forms on my site:
hidden link

1. I made the forms post type translateable:
hidden link

2. I made some custom fields (forms) translateable:
hidden link

3. The form fields showing up:
hidden link

But the "send"-Button is still not there. And when I translate the fields etc. nothing happens:
hidden link
hidden link

I have 2 major problems. Imho the blocks are not registered in WPML? And how to choose the correct form in ATE? This time I set it manually but the Form was still not translated:
hidden link

Happy to hear from you!

Tobi

Symptoms:
Not compatible at all

Questions:
Are the blocks not registered in WPML?
How do I choose the correct form in ATE?

October 7, 2024 at 3:48 pm #16262774

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your patience.

Here is the ticket and the sandbox site. hidden link

October 7, 2024 at 4:12 pm #16262875

Thomas

EDIT: Can you please remove the images from my first post? Thank you!

I created 2 Kadance Avanced forms with different blocks (custom post type):
hidden link

And integrated them into these pages with the advanced forms block:
hidden link

Happy to hear from you again :)!

October 7, 2024 at 4:32 pm #16262955

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for responding.

I've translated the form located at hidden link . It displays the correctly translated form, despite showing "Unknown Selection," as depicted in the attached screenshot.

It appears that the issue may be specific to your side for some reason.

Why do you have Kadeance Element (kadence_element) in the WPML > Settings > CPT Translation but it's not showing on my end? Also, it could be caused by some kadeance settings. Could you check?

Screenshot_3.png
October 7, 2024 at 4:48 pm #16263018

Thomas

Kadence Element is for example to display an alternative footer. I activated this on the sandbox site.

Yes the unknow selection issue is the only issue left...

EDIT: There are still some strings not translated. But it's solved with:
</key>
<key name="helpText">
</key>

October 7, 2024 at 5:07 pm #16263066

Thomas

Help Text was easy but how to add the options values?
<div class="wp-block-kadence-column kadence-column68_ad3317-eb"><div class="kt-inside-inner-col"><!-- wp:kadence/advanced-form-select {"uniqueID":"1a1997-86","formID":"68","label":"Option 1","options":[{"value":"","label":"Option Eins"},{"value":"","label":"Option Zwei"}]} /--></div></div>

kadence-formss.jpg
October 8, 2024 at 10:08 am #16264857

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for your patience.

I've incorporated custom XML Configuration, so it should be functioning correctly now. Have you had a chance to review whether any settings in Kadeance might be hindering the form from operating on your translated page?

In my sandbox, the form displays the correctly translated version, despite showing "Unknown Selection" in the translated page editor.

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="kadence/advanced-form-text" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-textarea" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-submit" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-telephone" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-email" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-file" translate="1">
      <key name="label">
      </key>
      <key name="placeholder">
      </key>
      <key name="helpText">
      </key>
    </gutenberg-block>
    <gutenberg-block type="kadence/advanced-form-select" translate="1">
      <key name="label" />
     
      <key name="helpText"/>
       <key name="options">
        <key name="*" />
      </key>
    </gutenberg-block>
   
    <gutenberg-block type="kadence/advanced-form" translate="1">
      <key name="id">
      </key>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>
Screenshot 2024-10-08 at 6.06.30 PM.png
October 8, 2024 at 10:46 am #16265005

Thomas

Thank you Kor!
This helps me alot for other use cases :)! I now udnerstand how to set up the xml file and make Blocks translateable :).

Can you please remove the first image of the first post? Because of the private customer information :). Thank you for this!

The forms on my website are translated too. I have the exact same behavior like on the sandbox site:

"In my sandbox, the form displays the correctly translated version, despite showing "Unknown Selection" in the translated page editor."

Do you think it is better to ask the developers why this is happening? Or let it be.

Have a great day and thank you,
Tobi

October 8, 2024 at 11:00 am #16265066

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thank you for your response.

I'm glad to hear that was helpful. Regarding the issue you're facing on your website but not in our sandbox, I can continue the investigation; however, I will need access to your site since the problem is occurring only there. If you’re comfortable manually editing the translated page and selecting the form, you can go ahead and mark this ticket as resolved.

October 8, 2024 at 11:07 am #16265081

Thomas

Hi Kor,

Can you please remove the first image of the first post? Because of the private customer information :). Thank you for this!

I think you misunderstood me :).

On my website exactly the same happens like in your sandbox :). The form is translated that is fine!

Only this happens:
"I've translated the form located at hidden link . It displays the correctly translated form, despite showing "Unknown Selection," as depicted in the attached screenshot."

Do you think it is better to ask the developers why this is happening? Or let it be.

October 8, 2024 at 11:09 am #16265084

Kor
Supporter

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply.

I've removed the images. Well, since it's working as intended. Just let it be.

October 8, 2024 at 11:11 am #16265088

Thomas

The issue is resolved :)! Thank you!