Problem: The client is working on a multi-language project using WPML and needs to create custom language codes (e.g., fr_ml for French, de_ml for German) for their website. They are concerned about how these custom codes will affect translations sent to the third-party service Lilt and whether it impacts the default locales. Solution: 1. If you're using custom language codes, you need to inform us so we can map these codes in our proxy. Please contact us with the codes and corresponding languages. Additionally, you should notify the translation service (Lilt) to make necessary adjustments. 2. The custom language code itself does not significantly impact the process as long as it is correctly mapped. However, it might affect existing translations of plugin/theme strings that are specific to standard language codes (e.g., fr instead of fr_ml). 3. We will handle the mapping of these custom language codes in our proxy to ensure they correspond to the correct languages.
If this solution does not resolve your issue or seems outdated, we recommend checking related known issues at https://wpml.org/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 open a new support ticket.
Problem: You are trying to send items for translation using Translation Manager with Crowdin as your translation service. After selecting items and adding them to the Translation Basket, you attempt to send them for translation. However, you receive a 'Rollback jobs... Batch rolled back' message. Solution: First, ensure that the language you are trying to send to Crowdin is properly set up within Crowdin. In this case, the issue was that Spanish was not configured in Crowdin, causing WPML to fail the transmission. If you're experiencing this, we recommend checking the language setup in your Crowdin account.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please visit our known issues page and verify the version of the permanent fix. Ensure you have installed the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket for personalized assistance. You can do so here: WPML support forum.
Problem: The client is experiencing issues with missing paragraphs when sending blog posts from their site to Smartling for translation. Some paragraphs are not returned and need to be manually added to the string translator. Solution: We recommend downloading the translated XLIFF file from Smartling to check if the translations exist. Additionally, creating a test page with just two strings can help determine if the problem persists. If these steps do not resolve the issue, we suggest providing temporary access (wp-admin and FTP) to your site for further debugging. Please ensure to back up your site before providing credentials, or use a test site if possible. For more details on providing access safely, visit https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is trying to manage translation jobs on their site using WPML and submitted a job for translation but included languages other than 'English to Dutch'. When attempting to cancel the unwanted translation items, they receive an error stating 'This action does not apply to any of the selected translation jobs'. Solution: Once translation jobs are sent to the automatic translation service and are in the translation service system, they cannot be canceled from the website end; they can only be canceled by the translation service. If the translation jobs were sent to a local translator via the website, they could be canceled directly on the site. To attempt to resolve the issue: 1. Navigate to WPML->Support->Troubleshooting-> Reset professional translation state. This feature stops any translation work currently in progress but will cancel all jobs, not just the specific one. 2. For canceling a specific job, log in to your memoQ dashboard and try canceling from their dashboard. If unsuccessful, contact the service provider directly with the specific job ID for cancellation.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
