Translations not sent to Translation Service (CrowdIn), even though I can find those.

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was unable to send a template string to their Translation Service (CrowdIn). The string appeared in the basket before sending but got lost during the process. This issue did not occur with a similar string in a different template.

Solution:
We investigated and suggest the following steps:
1. Verify if the template "Front Landing TMPL" has been sent to Crowdin and check if it has been translated and delivered.
2. Check the WPML Jobs tab for the status of the translation jobs. If jobs were opened in a local translator and then canceled, they might not appear in WPML.
3. If you manipulated the database and emptied the icl_translate_jobs table, this could cause the issue. Instead, follow our recommended method to reduce the size of WPML tables: Reducing the size of WPML tables.
4. For the specific string that is not being sent, you can:
A. Copy the translation from another language, as done with Bulgarian.
B. Send the template to a local translator and use the Classic Translation Editor.
C. Delete the problematic string in String Translation, update the template, and translate it again, possibly using translations from a similar string.

Please ensure to back up your site before making any changes.

If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your case, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please open a new support ticket in our 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.

Tagged: Translation Service

This topic contains 20 replies, has 2 voices.

Last updated by Itamar 8 months, 2 weeks ago.

Assisted by: Itamar.

Author	Posts
March 21, 2024 at 7:14 am #15434475
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi, Our Translation Service expert has investigated this issue. Here are our findings and suggestions. 1- In the translation proxy, we can see that this template "Front Landing TMPL" is sent to Crowdin and has been translated and delivered to the 21 languages found on the site, and the batch name is "15.03.new.front.tmpl.landing\|en". 2- Those jobs mentioned in our first point are not shown in the Jobs tab in WPML except for the Estonian, and it shows that it's opened in a local translator, as shown in the screenshot helenpuhu.png. Our conclusion for this part is that you opened the jobs in a local translator and canceled them, and that's why we can't see the other jobs in WPML. We are not sure why they are still showing as being in progress in the string translations tab. It might be because of the manipulation you did in the DB. ("...we have emptied the icl_translate_jobs table). 3- Furthermore, we checked the translation you added for this string in Bulgarian, and we found that you just copied the original content, as shown in the screenshot string-copied-from-original.png. We also checked the translated XLIFF file from the translation proxy and found that the strings were copied from the original to all the other languages. We can see that the Bulgarian string is translated on the front end. Please see the attached screenshot bl-string.jpg. The fact it is translated on the front end may be due to caching. Your site is hosted on WPengine, and they use caching heavily. This also implies that in the past, this string had been translated. We can also see that you have the same string, maybe in another template, already translated into all the other languages. (Except German, which you have its own template for this page.) Please see the attached screenshot dnogkg_text.jpg. This is a good point because you can use the translations from this string to string in the template in question. And you don't need to send them to Crowdin again. In conclusion, to translate these strings, try one of the following: A. Do exactly as you did with the Bulgarian translation. B. Alternatively, you can send the "Front Landing TMPL" template to a local translator and translate it using the Classic Translation Editor. Try it with only one language, see how it goes, and proceed. C. In Strings Translation, delete the string (Domain:bricks-196274 Name:jgguac_text) only. Update the "Front Landing TMPL" template, which should make the string show the string again. Now, the gear icon should not show, and the plus icon should show. Then, translate it again. You can use the translations from the other string - Domain: bricks-1078 Name: dnogkg_text. ** Important! Please make a full site backup (files and DB) before you proceed with those steps** Regards, Itamar.
March 21, 2024 at 8:52 am #15434978
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi again. In addition to the above, our second-tier supporter adds the following information. Emptying the icl_translate_jobs table can cause multiple issues. This is not recommended; they can use our recommended method to reduce the size. Please see this errata page. https://wpml.org/errata/reducing-size-of-icl_translate_job-icl_translate-and-other-wpml-tables/ If jobs are missing, those will be shown as being in progress in ST. If they can't restore the DB, sending the jobs again should do the job. ** Important! Please make a full site backup (files and DB) before you proceed with those steps** Regards, Itamar.
March 21, 2024 at 1:22 pm #15436438
kalleV-3	Thank you for your investigation. Some questions and feedback to your suggestions. 1&2 Yes, I think I previously confused the template with the original one that I had. I created the "Front Landing TMPL" so I wouldn't mix it up with "LANDING PAGE default TMPL", which we actually use on our landing page right now. - What is the local translator , is it the ATE ? If we only open it in ATE and do not click the "Complete" button, the template is already ruined as in set to "In progress"? - Is there a proper way to reset the state for translations for a single template "Front Landing TMPL" ? To cancel all "In progress" jobs ? - If there's no way to reset it in WP, what tables in DB are involved for the translation's status' ? Can I maybe mark the status somewhere done or remove some entries manually ? 3. Yes, I tried to find a workaround for "LANDING PAGE default TMPL" , so I added the translations in String Translations tab manually for all of the languages yesterday. Unfortunately, it only displays Bulgarian translations. I tried cleaning the cache both for WPML and WP Engine, but it doesn't update newly added translations to the template . - Is there a manual force refresh? - Is there a difference between ATE and Classic Translation Editor ? In settings it's recommended to have ATE, but we shouldn't use it anyway as we use CrowdIn Service and otherwise the service translations will be overwritten. And thanks, it seems the solution to delete the translation string and replace it with new content and manually copying over the translations worked. Although another issue arose from template rendering, but not sure if it's tied with Bricks or WPML.
March 21, 2024 at 5:46 pm #15437986
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi, First, I'm glad to hear that my suggestion about the string worked. I'll now answer your questions. What is the local translator , is it the ATE ? A local translator is a user of your site assigned to be a translator. It is not a Translation Service like CrowdIn or automatic translation. A local translator can translate with the Advanced Translation Editor, the Classic Translation Editor, or the WordPress editor. It all depends on the settings. Here is the relevant guide. https://wpml.org/documentation/translating-your-contents/how-to-set-up-local-translators-and-language-pairs/ If we only open it in ATE and do not click the "Complete" button, the template is already ruined as in set to "In progress"? I'm unsure what you're asking here. In any case, this behavior is by design. As long as you don't complete a translation with the Advanced Translation Editor, the translation will remain in progress. Is there a proper way to reset the state for translations for a single template "Front Landing TMPL" ? To cancel all "In progress" jobs ? Here is the relevant guide. https://wpml.org/documentation/translating-your-contents/#how-to-cancel-translation-jobs If there's no way to reset it in WP, what tables in DB are involved for the translation's status' ? Can I maybe mark the status somewhere done or remove some entries manually ? I strongly suggest you don't manipulate the translations in the DB. For your information, here is our article about WPML's DB tables. https://wpml.org/documentation/support/wpml-tables/ Is there a manual force refresh? There isn't such a feature from WPML's side. In WPML's troubleshooting section, you can try the 'Clear the cache in WPML' option. But I'm unsure if this is what you are looking for. This option is in WPML -> Support -> Troubleshooting (link). * Please backup your database before using this.* Is there a difference between ATE and Classic Translation Editor ? There are many differences. You can read about the editor here. https://wpml.org/documentation/translating-your-contents/using-the-translation-editor/ https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/ One of the main differences is that when you use the Advanced Translation Editor, the translations are done on an external server - our Advanced Translation Editor server. Then, when completed, they are delivered to your site. The translations with the Classic Translation Editor are done on your WordPress site. Regards, Itamar.
March 22, 2024 at 8:23 am #15439179
kalleV-3	Thanks for the clarifications. I think we are to avoid using those translation editors , because we want to use external service for that. And using translation editor turns the content into in-progress state which doesn't sync the content anymore between languages. And there's no way to resolve it without sending the content again to CrowdIn. The cancel jobs work 50% of the time from UI , also the Cancel all in progress jobs does nothing under troubleshooting for us. I know about the clear cache button and this unfortunately doesn't seem to do much either when we are having trouble with synching the content. That's why I was looking for a way to reset everything or remove it from DB manually. To have a clean slate of translation jobs. Have a blessed day!
March 24, 2024 at 9:40 am #15443705
Itamar Supporter Languages: English (English ) Hebrew (עברית ) Timezone: Asia/Jerusalem (GMT+02:00)	Hi, Thanks for the further input you provided about this case. And thank you for marking this thread as resolved. Have a great week! Regards, Itamar.