Problem: If you're experiencing issues where custom fields appear empty in translated posts despite being set to 'copy' in WPML settings, you might be facing a common synchronization problem. Solution: We recommend trying to open any of the original posts and resaving them. This action can often trigger the synchronization process needed to populate the custom fields in the translated versions. Alternatively, you can use the bulk edit feature to resave multiple posts at once. For detailed instructions on how to perform bulk edits, please visit Bulk Edit Documentation.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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 problem persists, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client is facing issues with maintaining SEO settings after translating pages using WPML and Yoast SEO. Specifically, the schema settings like 'Page Type' are not being preserved in the translated versions. Solution: 1. Navigate to WPML > Settings > Custom Field Translation and click on Show system fields. 2. Set the following fields to Copy:
_yoast_wpseo_schema_article_type
_yoast_wpseo_schema_page_type
3. Reapply the translation for your page. Depending on your setup: - If using Translate Everything Automatically, edit and save the original content to trigger an automatic retranslation. - If manually translating, use the WPML Translation Editor to open and save the translation again. This process might need to be repeated for each page missing the settings. For more detailed guidance, refer to the documentation on Translating Custom Fields.
If this solution does not resolve your issue or seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and consider opening a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with translating hard-coded theme strings using WPML, and facing problems with permalinks and slugs resulting in 404 errors, this might be due to the theme not being properly scanned for translatable strings. You might notice that despite using the 'Look for strings while pages are rendered' setting and regenerating .mo files, the translated strings do not display correctly, showing in the default language instead of the expected translation. Solution: We recommend going to your WordPress dashboard, navigating to WPML > Theme and Plugins Localization, and selecting the plugin or theme containing the problematic code. Click the scan button to ensure the code is scanned properly. After scanning, return to the String Translation page and search for the string in question to check if there's an untranslated instance. For detailed guidance, visit finding strings that don't appear on the string translation page. If the issue persists or 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.
Problem: You are trying to translate a pattern on your site and have successfully translated it into SK, but you are unable to send it for translation to EN. This pattern is used sitewide on a massive amount of pages. Solution: Ensure you are following the correct workflow by creating a new job for the pattern at WPML > Translation Management > Dashboard and accessing the translation via WPML > Translations. Please avoid editing translations of templates, template parts, menus and patterns of Block Themes directly inside Site Editor, as this could break your site's display conditions.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at WPML support forum.
Problem: El cliente no puede traducir el footer de su sitio web, que no está creado como una plantilla sino directamente en el maquetador de temas. A pesar de haber realizado las traducciones en cadenas, el footer sigue apareciendo en castellano. Solution: 1. Incrementar el límite de memoria de WordPress a un mínimo de 256MB. Esto se puede hacer añadiendo el siguiente código en el archivo wp-config.php:
Colocar este código encima de la línea /* That's all, stop editing! Happy blogging. */. 2. Verificar si el footer está creado como una plantilla y si dicha plantilla se ha traducido correctamente siguiendo las instrucciones en https://wpml.org/documentation/plugins-compatibility/elementor/#translating-elementor-templates. 3. Si el footer no está como plantilla, ir a WPML -> Administración de traducción, filtrar por 'Plantilla' (la última), seleccionar el Footer, enviarlo a traducir, y luego en la canasta de traducción asignarlo a un traductor o añadir las traducciones directamente desde la edición del post.
Si la solución proporcionada no resuelve el problema o parece desactualizada, recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tiene instaladas las últimas versiones de temas y plugins.
Problema: El cliente necesitaba traducir la URL de un video configurado como fondo en un contenedor de Elementor Pro y enfrentaba problemas con la activación del OTGS Installer y la traducción del video. Solución: 1. Se explicó que el OTGS Installer solo se activa durante la primera instalación de los plugins de WPML y luego se desactiva automáticamente, lo cual es un comportamiento esperado. 2. Se recomendó aumentar el límite de memoria de WordPress a un mínimo de 128Mb agregando el siguiente código en el archivo wp-config.php:
3. Para traducir la URL del video, se sugirió utilizar el Editor de Traducción Avanzado (ATE) y seguir los pasos de la guía sobre traducción de enlaces externos en https://wpml.org/es/faq/como-puedo-traducir-enlaces-en-wpml/#traduccion-de-enlaces-externos. 4. Finalmente, se accedió al sitio con las credenciales proporcionadas y se editó manualmente la página en inglés con Elementor para cambiar la URL del video, resolviendo así el problema.
Si esta solución no resuelve tu problema o parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
