The client is experiencing an issue where changes made to an English page, specifically adding a new h1 tag and an icon, are not being reflected in the translated versions without incurring additional full translation charges.
Solution:
We identified that the main issue stems from the site not being connected to the Translation Memory before making these changes. To resolve this, we recommend connecting your sites to the Translation Memory to ensure translation consistency and avoid similar issues in the future. For detailed instructions on how to connect your sites, please refer to our guide on Automatic Translation Subscription for Multiple Sites.
Additionally, it's important to ensure that during migrations or site copies, the sites are correctly connected to the Translation Memory. This step is crucial for maintaining translation consistency across different environments.
As a one-time gesture, we have deposited 300,000 credits into your account to assist with the translations.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problema: Estás intentando traducir un post y te indica que no tienes créditos, aunque tienes 18k+ disponibles. Además, experimentas un error recurrente en los logs que dice 'Api error missing resource: No sitekey found for this website', incluso después de actualizar el plugin y registrar nuevamente el sitio. Solución: Hemos realizado ajustes por nuestra parte y ahora deberías poder ver los créditos en tu sitio. Si el error de la llave de registro del sitio sigue apareciendo, te recomendamos volver a registrarlo. Por favor, confirma si el problema se ha resuelto.
Si esta solución resulta irrelevante porque está desactualizada o no aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: You have set up WPML on your site and configured it to publish translations immediately and skip reviews, designating yourself as the local translator. However, translations are stuck in the translation job queue at 100%, and upon saving, the status remains as a 'gear' icon, indicating a need for review by a local translator, creating an endless loop where you cannot publish translations. Solution: We recommend performing a reset of the WPML settings. Please navigate to WPML --> Support --> Troubleshooting --> Reset. After resetting, reconfigure your settings and check if the issue with publishing translations is resolved. If this solution does not resolve your issue or 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing issues with URL translations on your WooCommerce shop's main page using WPML. After making changes and refreshing the page in each language, the product links revert to the site's default language (German), instead of maintaining their respective language URLs. Solution: 1. Ensure that each menu item has its translated URL added to the corresponding translated menu. This adjustment will help maintain the correct URLs for each language after page refreshes. 2. Check if the products have complete translations for each required language. Missing translations can cause the URLs to revert to the default language. You can do this by editing the product and verifying the translations.
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 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 at WPML support forum.
The client was experiencing issues with translating content using WPML on their website. Specific problems included difficulties with using ALT+10 and higher for HTML formatting in translations, linking words, and locating categories in ACF for translation.
Solution:
We advised the client on how to handle HTML formatting in translations using the Advanced Translation Editor (ATE). For instance, to apply formatting:
Select the text needing formatting.
Use the ALT key combinations to apply HTML tags.
e.g..
ALT + 1 for <span></span>
ALT + 2 for <strong></strong>
We also updated the ATE server to ensure the ALT button appears only for the
<strong></strong>
tag, improving the interface for entering HTML tags in translations.
Additionally, we made a backend adjustment on the German version of the homepage to refresh the translation settings, which resolved the issues with homepage translation.
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. If problems persist, please open a new support ticket.
Problem: The client reported an issue where the URL field appears empty when editing translations through the WPML translation editor, despite the URL slug being previously translated and set. This occurs even though the translation completion shows 100%. Solution: We explained that the URL field appears empty because when the page was initially translated, the option for translating slugs was already set to 'translate'. However, slugs do not contribute to the translation completion percentage, which is why the page shows as 100% complete. The advanced translation editor does not save slugs in the translation memory, so when the page is manually edited later, the URL field appears empty. If it is not filled in, it defaults to copying from the Italian version as it does not have the French slug in memory. We also noted that any changes to this behavior would apply only to content not yet translated and that changes are not typically retroactive. We do not expect changes to occur soon, but updates will be communicated via email when new versions are released.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket.
Problem: You are using ATE for translations on your site. After clicking 'complete translation', the icon changes to a gear icon instead of the expected pen icon. Solution: We have applied a fix to resolve this issue. Please make a small change in the original language content and then update the translations. This method has been tested and should ensure that the pen icon appears correctly after completing a translation in ATE.
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: You are trying to add a French translation to a post using the WPML plugin. After completing the translation and pressing 'Complete translation', the Pencil icon shows it is applied. However, upon refreshing the page, the Pencil icon disappears, and the + button reappears, with the French translation still missing. Solution: If this issue is only occurring on a specific page, it might be due to corruption on that page. We recommend trying to duplicate the page and then attempting the translation on the duplicated page. Please check if this resolves the issue.
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 problem persists, please open a new support ticket with us for further assistance at WPML support forum.
Problem: You are trying to create a translation for a page using WPML, but when you click the + icon to start the translation, it redirects you to the WPML dashboard and the page fails to load. Additionally, you encounter an error stating 'This website is under heavy load (queue full)'. Solution: First, ensure that your website is not experiencing high traffic that could be causing the server to reach its capacity. If the traffic is normal, we recommend clearing the cache on your website, server, and browser as these can sometimes resolve issues of pages not loading correctly. If the problem persists, it might be due to a temporary server issue, in which case, trying again after some time may be beneficial.
If these steps do not resolve the issue, or if the solution provided here becomes outdated or does not seem applicable to your case, please visit our known issues page to check for any related issues. Also, ensure that you have the latest versions of themes and plugins installed. If the problem continues, we highly recommend that you open a new support ticket with us for further assistance.
Problem: If you're trying to translate content inside a Custom HTML Block in WordPress using the Advanced Translation Editor and find that the Custom HTML Block is not available for translation, this is because the Advanced Translation Editor is not designed for translating non-visual elements like HTML. It automatically copies the markup over to the translation, allowing only the included text to be translated. Solution: We recommend using the Classic Translation Editor, which supports HTML translation. You can learn more about using the Classic Translation Editor here. Alternatively, you can switch to the WordPress Editor for translating this content. This allows you full control over the HTML. For guidance on how to use different translation editors for different pages, please visit this link.
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. Should you need further assistance, please do not hesitate to open a new support ticket here.
Problem: If you're experiencing issues with translating a product using WPML, where the translation process has failed multiple times, and you're also unable to find an ACF custom field (specifically an oEmbed field with a YouTube link) in the ATE translations, follow these steps. Solution: 1. Navigate to WPML --> Translation Management --> Jobs and cancel the existing translation jobs. 2. Go to the original product, update it, and attempt the translation again. 3. If the issue persists, check the error logs by going to WPML --> Support --> Error logs for further insights. For translating the YouTube link in the ACF oEmbed field, search for the link in the translation editor as outlined in our documentation: https://wpml.org/faq/how-to-translate-links/
If these steps do not resolve your issues, or if the solution seems 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. Additionally, you can open a new support ticket for personalized assistance at our support forum.
