[Waiting for user confirmation] The translated forms are broken

Hi,

I've discussed this issue with our compatibility team. It has been brought to my attention that his problem has already been reported to us and escalated to our developers. You can see a reference for this in another forum ticket here: https://wpml.org/forums/topic/page-is-not-translated/page/2/#post-17358033.

Adding an equal sign before the placeholder text should solve this problem. To resolve this issue, please follow the steps below. If a

1. Edit the original "eonyx Contact Form_equivalent width" contact form on your site. You will see its code is this:

[email* customer-email placeholder "Your E-mail (required)"]


[text customer-phone placeholder "Phone Number"]


[textarea* customer-message placeholder "Message"]


[submit class:fusion-button class:fusion-xlarge, class:button-default class:"send"] 

2. Change it by adding an equal sign before the placeholder text, like this.

[email* customer-email placeholder="Your E-mail (required)"]


[text customer-phone placeholder="Phone Number"]


[textarea* customer-message placeholder="Message"]


[submit class:fusion-button class:fusion-xlarge, class:button-default class:"send"] 

3. Click the Save button. This will also trigger a change to the form in other languages, and you will see a circled arrow icon next to them.

4. Edit the translations of the form and translate it manually or automatically.

**** Important! Please make a full site backup (files and DB) before you proceed with those steps****

This should fix the problem.

Please let me know if you have any further questions or need help with this.

Regards,
Itamar.

Hi,

Thanks for following my suggestion.

You are right, the workaround causes the problems you mentioned. In the form's default language, the placeholder does not disappear when new text is inserted into the field. And in the translated form, indeed, the fields are showing, but the placeholder text does not show at all. I was able to replicate this issue on a test site, and you can view it here: hidden link.

I'm consulting our compatibility team about this and will keep you updated here.

I appreciate your patience.
Itamar.

Hi,

Yes, we have a way for you to correct this problem until our developers release a fix for it in WPML's Advanced Translation Editor. To proceed, follow these steps.

1. Edit the translated form with the other language. For example, in French edit the 'eonyx Contact Form_equivalent largeur' form here: hidden link

2. Remove the equal sign (=) and replace 'espace réservé' with 'placeholder'

3. Click the save button.

So, for example, currently your French form 'eonyx Contact Form_equivalent largeur' has this code (first three lines):

<p>[email* espace réservé customer-email "Votre E-mail (obligatoire)"]</p>

<p>[text   customer-phone placeholder="" "Numéro de téléphone"]</p>

<p>[textarea*   customer-message placeholder Message"]</p>

After the fix, it should be like this:

<p>[email* customer-email placeholder "Votre E-mail (obligatoire)"]</p>

<p>[text   customer-phone placeholder "Numéro de téléphone"]</p>

<p>[textarea*   customer-message placeholder "Message"]</p>

Please let me know if you require additional assistance or have further questions regarding this workaround.

The issue has been escalated to our developers, and we will update you here once the version with the fix is released.

Regards,
Itamar.

Hi,

Thank you for your feedback.

In our internal tracking of this issue, I can see that our developers have set a high priority for this issue, so I assume they will fix it from our side as soon as possible.

I understand the suggested workaround might not be the ideal way of correcting this issue. But for each case, if possible, we try to provide a workaround so our clients won't get stuck. This time, I went the extra mile and fixed it for you on your site. The translations of the 'eonyx Contact Form_equivalent width' form into all the languages are now fixed. For example, see the French form: hidden link. Please see the attached screenshot.

I'll update you here once there is a new version of the Advanced Translation Editor with the fix for this.

Regards,
Itamar.