Problem: The client needs to control the publishing status of pages translated through WPML and a third-party service, Smartling. Specifically, the client wants to prevent automatic publishing of translated pages and ensure that corrections to already published translations do not revert them to draft status. Solution: 1. To prevent a translated page from being automatically published upon receipt from a translation service, you can adjust the settings in WPML. Navigate to WPML > Settings > Multilingual Content Setup Tab > Translated documents options. Here, you can set 'When you receive completed translations' and 'When you publish the original post' to save translations as drafts instead of publishing them automatically. 2. If you are correcting a typo in an already published translation, the status of the page will not change to draft; it will remain published. 3. Currently, it is not possible to set different automatic actions (publish or draft) for different types of posts. However, we have noted your interest in this feature and will consider it for future updates.
Please note that the solution provided might be outdated or not applicable to your specific case. 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 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 was unable to see the 30k translation credits they moved to their site, despite having a custom integration with Smartling and custom mapping for language codes. Solution: We explained that when WPML is initially installed, an automatic translation account ID is created. If WPML is uninstalled/reset, or if WordPress is reinstalled from scratch, a new automatic translation account ID is generated, and the credits may remain in the old account. We found the 30k credits in an older account and another 2k credits in a different account. We then directly assigned these credits to the client's current automatic translation account. We advised the client to check under WPML > Translation Management > Tools to see if the credits are now visible.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 problem persists, please open a new support ticket at WPML support forum.
Problem: The client was unable to see certain German (DE) language strings on their site unless the option 'Look for strings while pages are rendered' was activated. This issue was linked to a conflict with an old custom language that shared the same language code (de_DE) as the new one.
Solution: Client resolved it by deleting the conflicting old custom language. After removing it, the client needed to go into one string from a domain and resave it in the German language.
Additionally, we suggested checking other methods to bring strings into String Translation without relying on the 'Look for strings while pages are rendered' option. You can find more details in our guide on finding strings that don't appear on the String Translation page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client needed specific language codes mapped in WPML for integration with Smartling. The required mappings were: fr to fr-fr, de to de-de, pt to pt-br, and es to es-es.
Solution: We successfully completed the mapping as requested. We recommend the client to verify the mappings by checking the language settings in WPML.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please do not hesitate to open 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, you can visit our support forum at WPML Support Forum.
Problem: The client has a custom ACF block called Header Block with multiple fields (title, subtitle, content, button label, etc.), but only the button label is showing, and the other fields are not. The client is following the WPML documentation for translating sites built with ACF but is facing an issue because the field names are not unique across blocks.
Solution: We recommend ensuring that all field names are unique. This is a known limitation with ACF and WPML, as WPML handles custom fields by name, which are stored in the meta tables. Therefore, translation preferences are set by field name, necessitating their uniqueness. Here are some resources to help understand the importance of unique field names:
If this solution is not applicable due to it being outdated or not relevant to your case, we 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 you still need assistance, please open a new support ticket.
