Skip Navigation

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

Problem:
The client is unable to find 'Field Placeholder' texts in the Advanced Translation Editor (ATE) for a Kadence Form block, even after updating their XML file.
Solution:
We recommend removing any custom XML configurations for the Kadence Blocks, as we already maintain the default configurations which can be found here: WPML config for Kadence Blocks. After removing the custom config, edit the placeholder text directly in the form on the original content and then reopen the translation editor. This should allow the placeholder to be sent to the translation editor as an HTML attribute without any issues.

If the issue persists, we suggest checking the related known issues at 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. If the problem still remains unresolved, please open a new support ticket at WPML support forum for further assistance.

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 1 reply, has 2 voices.

Last updated by Andreas W. 6 months, 1 week ago.

Assisted by: Andreas W..

Author Posts
May 17, 2024 at 10:07 am

pamelaW

Hi,
I have some "Field Placeholder" texts that cannot be found in the ATE. It is in a Kadence Form block. I have updated my XML-file:

//label
//placeholder
//ariaLabel
//button
//span
//textarea/@placeholder

hidden link
hidden link

May 17, 2024 at 11:48 am
May 17, 2024 at 8:57 pm #15641055

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

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

Hello,

You should not need any custom config for the Kadence Form.

We do maintain the default config for Kadence Blocks which can be found here:
hidden link

I ran a test on a new test site and the placeholder was sent to the translation editor as an HTML attribute without any issues.

Please remove your custom config, then edit the placeholder on the form on the original content and open the translation editor again.

If this will not solve the issue, please let me know.

Best regards
Andreas

placeholder.png
May 20, 2024 at 6:25 pm #15647133

pamelaW

Thank you Andreas,
I removed the custom config, and now it's working.

Vielen Dank!

Pamela