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.
Our next available supporter will start replying to tickets in about 7.48 hours from now. Thank you for your understanding.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 7:00 – 15:00 | 7:00 – 15:00 | 7:00 – 15:00 | 7:00 – 15:00 | 7:00 – 15:00 | - |
- | - | - | - | - | - | - |
Supporter timezone: Pacific/Easter (GMT-05:00)
This topic contains 25 replies, has 3 voices.
Last updated by danielM-3 2 days, 6 hours ago.
Assisted by: Ilyes.
Author | Posts |
---|---|
September 2, 2024 at 1:31 pm #16131905 | |
danielM-3 |
<b>Background of the issue: </b> <b>Symptoms: </b> <b>Questions: </b> second problem: when using the translation queue for multiple records, the “überprüfung”/verification does not work |
September 2, 2024 at 1:44 pm #16132101 | |
Nicolas V. Supporter
Languages: English (English ) French (Français ) Timezone: America/Lima (GMT-05:00) |
Hello, 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. 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! |
September 3, 2024 at 1:24 pm #16135889 | |
danielM-3 |
Dear Nicolas, 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: Thx! |
September 3, 2024 at 8:39 pm #16137831 | |
Nicolas V. Supporter
Languages: English (English ) French (Français ) Timezone: America/Lima (GMT-05:00) |
Hello, 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. Video: hidden link |
September 9, 2024 at 5:55 am #16153490 | |
danielM-3 |
Dear Nicolas, thank you very much for the video! I think that solves the problem regarding the frontend view of the translated post. But i just found another issue: When using the ATE to translate a post it seems breaks and paragraphs are being stripped from the richtext editor field after the translation is done. See the two screenshots attached. Can this be avoided somehow? Thank you! |
September 9, 2024 at 6:06 am #16153654 | |
danielM-3 |
Dear Nicolas, there's one more problem: 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. Thank you! |
September 9, 2024 at 12:05 pm #16156047 | |
Nicolas V. Supporter
Languages: English (English ) French (Français ) Timezone: America/Lima (GMT-05:00) |
Hello, 1. Regarding your first question, could the issue be that you're using the text editor instead of the visual editor? I noticed that there are no paragraph tags "<p>" or break tags "<br />" 2. As for ACF fields, configuring translation preferences for each field can be challenging. Let's begin by reviewing your current setup: - 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: For all other fields (including subfields of flexible content): |
September 9, 2024 at 2:08 pm #16157022 | |
danielM-3 |
Hi! 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? |
September 9, 2024 at 5:25 pm #16158151 | |
Nicolas V. Supporter
Languages: English (English ) French (Français ) Timezone: America/Lima (GMT-05:00) |
Hi Daniel, - The flexible_content fields should be set to "Copy", while the subfields should be set to "Translatable." |
September 11, 2024 at 4:34 am #16164043 | |
danielM-3 |
Dear Nicolas, 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). Maybe there's some setting missing for Italian? Thank you very much! Best regards, |
September 11, 2024 at 1:31 pm #16166772 | |
Nicolas V. Supporter
Languages: English (English ) French (Français ) Timezone: America/Lima (GMT-05:00) |
Hello, 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: 2. You can adjust the translation preferences directly on your production site: Steps: 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. |
September 12, 2024 at 5:19 pm #16173032 | |
danielM-3 |
Dear Nicolas, 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. Thank you! |
September 13, 2024 at 11:24 am #16175297 | |
Nicolas V. Supporter
Languages: English (English ) French (Français ) Timezone: America/Lima (GMT-05:00) |
Hello, 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. |
September 16, 2024 at 4:19 am #16181174 | |
danielM-3 |
Of course the admin url ends with /wp-admin 🙂 |
September 16, 2024 at 2:36 pm #16184480 | |
Nicolas V. Supporter
Languages: English (English ) French (Français ) Timezone: America/Lima (GMT-05:00) |
Hello, I can't access the staging site. I have the following error:
Could you please check that for me? |