Home›Support›English Support›[Resolved] Original string translation will be replaced when manually initiate page transla
[Resolved] Original string translation will be replaced when manually initiate page transla
This thread is resolved. Here is a description of the problem and solution.
Problem: The client encountered an issue where after updating a translation, the shortcode for a Fluent Form reverted to the original language shortcode instead of the translated one. The client had previously translated the shortcode using String Translation and added custom XML configuration and PHP code to make the shortcode translatable, but was unable to find the shortcode in the Advanced Translation Editor (ATE) window.
Additionally, we suggested that if the client is using the Divi builder, they could manually edit the second language page and ensure that the same shortcode/form from the default language page is present, allowing for manual adjustments as needed.
Please note that this solution might not be applicable if it's outdated or not relevant to your specific case. If you're experiencing similar issues and the provided solution does not help, we encourage you to open a new support ticket. We also highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us on the WPML support forum.
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.
I have found a strange issue. Hopefully, it will also be reproducible on your end.
I created the page where I put the fluent form via the short code (example [fluentform id="82"]), then I translated the page and via the string translation I entered the english version of the fluent form - [fluentform id="83"].
Everything was working fine, until I have to update the translation - something went wrong with the layout so I have to manually request for the translation - via the Translations menu - when I finish the translation, I found out, that the original string [fluentform id="82"], which I translated via the string translation to [fluentform id="83"] was again returned back to [fluentform id="82"].
This is not very convenient, because I when I forgot it, incorrect version of the form is displayed.
Thank you for contacting WPML support. While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with the first debugging steps or if I can help with the issue quickly.
This is expected as you should not translate page or update page content via WPML String translation, you should use the WPML translation editor, or if you wish to have different content you can disable it and use the manual translation method.
Note you should not mix the manual and WPML editor methods, as one will overwrite changes done by the other, you should choose one method and continue to use it.
I still cannot find the shortcode - then I tried to search for it - but nothing.
Then I just entered the ID - because it was in the XML code - and I was able to find it.
It is not very practical - as I need to remember that there is some fluent form on the page - and then I need to know its ID.
Would it be possible to display this ID directly on the page without the need to search for it manually?
I am just uploading the image where you can see the string with ID - I also tried to put there the translated form, and it was working fine.
Now, need to display this line directly on the translation page.
Yes, that is the way when you want to translate it via the WPML editor, and you explained the procedure correctly, there is no other way when using WPML editor. You need to search for ID and add translation for it in ATE.
As for showing the form directly on the page, as I have said before and my colleague in shared ticket, you can edit your 2nd page manually via Divi, and the same shortcode/form should be there as in your default language page and then you can make changes manually. I think this is what you are looking for.