This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with translating records using the WPML editor, where clicking the 'Abschließen' button redirects back to the original record instead of the translated version. Additionally, there are problems with ACF fields not being translated correctly, and line breaks and paragraphs being stripped from the translated content.
Solution: 1. Ensure you are using the visual editor instead of the text editor to maintain formatting such as paragraphs and line breaks. 2. For ACF fields, set the translation preferences appropriately: - Set 'Field Groups (acf-field-group)' to 'Not translatable' under 'WPML > Settings > Post Types Translation'. - Use 'Copy' for special fields like 'Repeater' and 'Flexible'. - Set subfields of flexible content to 'Translatable'. - For fields not requiring translation, use 'Copy' to keep the same value across translations. 3. Update the translation preferences and make a minor modification to the original page to trigger an update. 4. Check the 'Presentation' tab in the ACF field settings to ensure proper rendering of new lines and automatic paragraph addition.
If these steps do not resolve your issues or the solution seems outdated, we recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can also visit our support forum at 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.
<b>Background of the issue: </b>
I am trying to translate a record using the WPML editor on the site hidden link. I have been following the WPML documentation.
<b>Symptoms: </b>
When I click the 'Abschließen' button after translating a record, it sends me back to the original record instead of the translated version.
<b>Questions: </b>
Why does the 'Abschließen' button not take me to the translated record?
How can I access the translated record after using the WPML editor?
second problem: when using the translation queue for multiple records, the “überprüfung”/verification does not work
Welcome to the WPML support forum. Based on your screenshots, being redirected to the original content is normal behavior. Here's why:
- To translate content (page, post, custom post type), you click the "+" icon.
- This takes you to the Advanced Translation Editor (ATE) for translation.
- After completing the translation, you’re automatically redirected back to the original content.
This is intended, as editing translations directly in the WordPress editor isn't recommended. Also, returning to the original language allows you to continue working on other translations.
For your second question about the translation queue, I need a bit more clarification. Could you provide more details or share screenshots like before? A short video could also help greatly, you can use loom.com and share the link with me.
thank you for your reply! Is there any way in the workflow you described to get to the new translated content from the ATE?
Regarding the second topic:
In the attached screenshot you see the "Review" button. Is there a way to link the "review" button to the admin-url of the translated post? The frontend-link does not work for us because we use wordpress as a headless cms.
If I understand correctly because you're using WordPress as a headless CMS, you don't have access to the frontend review right?
I have recorded a short video where I explain two workarounds that will allow you to access the Advanced Translation Editor (ATE) without going through the frontend revision.
We are using ACF with the flexible_content field. In one flexible_content element, the subfields are not being translated in the ATE at all. See the 3 screenshots attached.
- Now, when you edit your ACF groups in the default language, this is where you determine the translation preference for each field. Here we are talking about the translation of the field value in "Custom Fields > Field groups".
I recommend setting the Multilingual mode to "Same fields across languages". However, if you use the "Expert mode" please follow these rules:
- "Copy" for special fields "Repeater" and "Flexible".
For all other fields (including subfields of flexible content):
- "Translate" for all the fields you want to translate such as texts, WYSIWYG etc...
- Use "Copy" if you don't want to translate the field but keep the same value, for example for colors, true/false, images etc...
1) I'm using the TinyMCE Editor for ACF textarea field (visual mode).
2) I changed the flexible_content field to "copy_once" and the factbox fields which do not get translated to "translate". Unfortunately they still do not appear in the ATE for automatic translation?
- The flexible_content fields should be set to "Copy", while the subfields should be set to "Translatable."
- Note that updating the translation preferences can take some time. You can monitor the progress via the WPML icon in your top admin bar.
- For a quick test, try applying these fields to a different page to check if the preferences are correctly set.
- Lastly, edit your original page and make a small modification to these fields; this should trigger an "update needed" on the translation.
thank you very much for your support! I tried these things.
1) "Factbox" element is not translated
I changed the fields to "copy" and "translate" and created a new post. See the attached screenshot. Now automatic translation works fine.
One important question: Is it save to change the module "factbox" from "copy once" to "copy" and the two content fields within from "copy once" to "translate" on a live site with existing content?
2) Line breaks / paragraphs get stripped during translation
I tried this again and wrote some text in a WYSIWYG editor field (see the screenshot attached). After automatic translation to English all paragraphs and linebreaks are stripped from the text.
Is there anything i can do about it?
3) Strange behaviour of translation workflow to Italian
Using the automatic translation from German -> English works fine (except the glitches mentioned above).
But when using automatic translation from Germen -> Italian the behaviour is strange. When i proceed with the auomatic translation and click on the "Abschließen" (Finish) button the page reloads, but the translation state does not update and the translation never get's finished (like it does with Englisch).
I'm not sure to fully understand as I'm not familiar with your site. Let’s tackle one issue at a time to keep things clear.
1. Based on your screenshot, I’ve added my comments to make sure we're referring to the same fields:
- The field type REPEATER should be set to "COPY."
- The subfields within that repeater should be set to "TRANSLATE."
Hopefully, that clarifies this part!
2. You can adjust the translation preferences directly on your production site:
- This won’t affect the repeater behavior: "Copy once" copies the repeater fields only when you create the translation for the first time, while "Copy" will ensure they remain identical every time you update the original.
- For the subfields previously set to "Copy once", the translation field will initially contain the original language text, but you will be able to manually update it with the correct translation.
Steps:
1. Go to "ACF > Field Groups" and edit the translation preferences.
2. Wait for the preferences to update.
3. Edit the original page (make a minor change, such as adding a space at the end of your fields) and save it.
4. Edit the translation using our translation editor.
Once we have resolved this issue, we can look into the paragraphs in the Visual editor. You can already check the “Presentation” tab for this ACF field, where there is an option to determine how to render new lines and automatically add paragraphs.
thank you! We will change the translation settings on the live server by the beginning of next week. Good to know from your side that changing the translation settings won't affect existing content / translated content at all.
Regarding topic 2 (line breaks): In some cases we have the opposite behaviour where additional linebreaks are added in the translation.
I'm not sure how the acf setting ("determine how to render new lines and automatically add paragraphs") could be a solution here? The problem with the added/removed line breaks only occurs when translating the content using the ate / automatic translation; it's not a problem with the original content.
Regarding the second issue, would you be able to give me access to the staging site?
I will activate a private field for your next answer where you can provide that information safely (this field is only visible by you and the support team). Don't share your own admin account, create a new one that you will delete when we finish troubleshooting.
IMPORTANT: Before we proceed, please backup your site and database.
Please also provide the field group name and a test page that is using it so I can run some tests.
I can't access the staging site. I have the following error:
This site can’t be reached
took too long to respond.
Could you please check that for me?
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.
