Background of the issue:
I'm trying to translate some select fields made with Elementor Pro form widget using the WPML 'classic editor'. The issue can be seen on this page: hidden link. Instead of a list of selectable options, I got only one single option with many ''.
For example:
PortoferraioLaconaLido di CapoliveriMarina di Campo - Camping Ville degli UliviMarina di Campo - City CentreMarina di Campo 200 meters from the Airport - Free shuttle serviceProcchioPick-up "at home"
Symptoms:
The select fields are not rendered correctly on the website frontend. Instead of each option being on a different row, I see a single row with all the options separated by '', making it impossible to select a specific option.
Questions:
Why are the select fields not rendering correctly after translation?
How can I fix the issue of options being displayed in a single row with ''?
Let me remind you I'm using the "Classic editor".
Just to let you know, I've manually edited every single form in its language on my website just to "fix" this issue, so right now you will NOT find this issue on my website. Obviously that's NOT a real fix for this issue, because right now I can't translate anymore my form in the "standard" way.
So, please try to find a fix in your sandbox website, ok?
thanks!
Currently, the only solution is to manually set the translations.
>> honestly that's NOT really a solution. I have a website with 4 languages, manually edit my form in every single language takes a lot of time. Please, let me know any other solution and workaround.
For example, can I solve the issue by translating again my form using the new WPML's Advanced Translation Editor? I don't like the new editor, but if it's the only possible solution I'm fine with it.
Ok, so I'm testing the new Advanced Translations editor and honestly I am a little surprised at the way fields that contain HTML code or other variables are handled... Does anyone really think that handling HTML tags and variables in this way is more handy?
Is there any way to use the new advanced editor while keeping the HTML tags and any other variable as simple plain text as in the old editor?
Is there any way to use the new advanced editor while keeping the HTML tags and any other variable as simple plain text as in the old editor?
I regret to inform you that it’s not possible to use HTML as plain text. We used this method because it’s more convenient for translating texts for users who lack HTML knowledge. This ensures that the layout remains intact.
Ok, I understand that you think this method is more convenient (I'm not really sure).
But I have to translate the content of the emails sent after the form is filled out, and this includes all the shortcodes that contain the various dynamic fields in the form. Now all these dynamic fields are not even shown in the translation editor, so how can I be sure they are entered correctly?
Do you really think that hiding things that used to be visible and editable is an improvement? At least you should give the option to choose whether to hide them or not, don't you think?
Honestly, I really can't believe you made the new "improved" editor in that way. Plese tell me there's something i can do to change it.
Hi, what I meant is that those dynamic fields are "not clear". I mean:
1. in the original language I have lots of shortcode like "[field id="field_scooter"]", ok?
2. but in the translation editor I have the same "wpcodeself" variable for every shortcode, so there is no way to see which shorcodes they correspond.
I understand that this new editor may seem more convenient for translating simple texts, but when you have to translate more complex texts that contain shortcodes or things like that, it is not intuitive at all. I guess you can at least provide a way to identify those shortcodes instead of giving the same "wpcodeself" name to all of them, don't you think?
Anyway, my situation is:
- I can no longer use the old translation editor, because it has a bug that you have no intention of fixing.
- So I am forced to use the new translation editor, which I don't like and is inconvenient for translating texts with shortcodes, since all shortocodes are shown with the same name.
Honestly, I am not happy at all about this situation because I have to waste my time trying to fix a problem caused by a bug in WPML that you can't or won't fix. And I really don't like the only solution you gave me, but since it is the only solution available I must necessarily settle for it.
But, again, I'm not happy at all. If you want to help me, please ask the developers if they are working on fixing the bug and if they know when a fix will be released.
Yes, I've already manually translated every single form in its language just to "fix" this issue, otherwise my forms would still be “broken”. But that's NOT a real fix for this issue in the long time, because from now on I would have to manually edit the forms in each language for every single change I make.
Please, fix the bug or at least provide an estimation release date for the fix.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
