Problema: Estás intentando añadir el idioma italiano a tu sitio web, que ya está traducido a varios idiomas, pero recibes un error de base de datos que indica un duplicado de entrada '4028-4' para la clave 'PRIMARY' al intentar insertar en la tabla
UgOYqAJP_term_relationships
. Solución: Este problema puede deberse a una posible corrupción en la base de datos. Te recomendamos crear un sitio staging con una copia de tu sitio en producción para realizar pruebas sin afectar el sitio en vivo. Si el problema persiste o la solución propuesta no es relevante porque está desactualizada o no se ajusta a tu caso, te sugerimos abrir un nuevo ticket de soporte. Además, te recomendamos encarecidamente revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.
Problem: The client was unable to locate and save translations for some custom strings on their website. Solution: We added the following XML code to the Custom XML Configuration tab in WPML->Settings to make the strings available for translation:
If you're experiencing a similar issue and the solution provided here does not resolve it, or if it seems outdated or not applicable to your case, 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: https://wpml.org/forums/forum/english-support/.
Problem: The client was trying to export translations, but they were not displayed correctly after export, even though they appeared fine when using the Advanced Translation Editor.
Solution: First, we checked the translation by using the WPML translation editor and confirmed it worked correctly. We then asked the client to follow these steps:
Go to WPML -> String Translation.
Enable the "Look for strings while pages are rendered" option.
Visit the page in the front end.
Disable the "Look for strings while pages are rendered" option.
We also provided direct links to the string translation pages for specific strings such as 'RESERVA AHORA' and '¿Cómo es la furgo?'.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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.
Problem: The client is experiencing issues with XLIFF files disappearing after export. They identified that they were exporting XLIFF 1.0 files, while their Phrase TMS supports XLIFF 1.20 and 2.0, which caused some strings not to be extracted for translation. Solution: If you're encountering similar issues with XLIFF files after export, we recommend checking the version of the XLIFF files you are exporting. Ensure that you export the correct version that is supported by your Translation Management System (TMS). In this case, the client should export either XLIFF 1.20 or 2.0 files to be compatible with Phrase TMS. If you're unsure of the steps to import/export XLIFF files from your site, please follow these steps: 1. Go to the WPML's Translation Management section. 2. Select the content you wish to translate. 3. Add selected content to the translation basket. 4. Send the basket to translation. 5. In the Translation Jobs tab, download the XLIFF file by clicking on the 'Export .xlf' button. 6. Make sure to select the correct XLIFF version that is compatible with your TMS. 7. After translation, import the XLIFF file back into your site. If this solution doesn't look relevant to your issue, please open a new support ticket with us, and we'll be happy to assist you further.
