Problem: Después de actualizar el sitio web y los plugins, incluidos WPML y ACF, los elementos como 'Field Group Title' y 'Field Label' de los grupos de campos personalizados creados con ACF aparecen como traducibles en las opciones de traducción de entradas, a pesar de que están configurados para copiarse en todos los idiomas y no deberían ser traducibles. Solution: Si estás experimentando este problema, te recomendamos añadir la siguiente línea en tu archivo wp-config.php:
Esta configuración evitará que los títulos y etiquetas de los campos personalizados de ACF aparezcan como traducibles en el editor de traducción avanzado. Puedes encontrar más información sobre cómo excluir etiquetas de campo en la documentación de WPML aquí: Excluyendo etiquetas de campo del editor de traducción avanzado.
Si esta solución no resuelve tu problema o parece no ser relevante debido a actualizaciones o diferencias en tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: Stai cercando di risolvere un problema sul tuo sito web dove appare un messaggio di errore come
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the marblex domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /public_html/wp-includes/functions.php on line 6114
Solution: Se stai riscontrando questo problema, ti informiamo che la notifica di errore non è direttamente collegata a WPML. Per maggiori dettagli, consulta la nostra documentazione qui. Se il problema persiste nonostante gli aggiornamenti, al momento non disponiamo di una soluzione alternativa.
Se la soluzione proposta risulta non essere pertinente, perché potrebbe essere datata o non applicabile al tuo caso, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di verificare i problemi noti su questa pagina, di controllare la versione della correzione permanente e di confermare che hai installato le ultime versioni dei temi e dei plugin. Per ulteriore assistenza, visita il nostro forum di supporto.
Problem: The client reported that the translation and synchronization of various navigation menus were not functioning correctly after a PHP version change. Solution: 1. We recommended creating a full backup of the site and asking the hosting provider to downgrade the PHP version to 8.2, as not all WordPress functionalities are compatible with newer versions. After downgrading, the client should verify if the issue was resolved. 2. We also advised applying a workaround described on the errata page to address string translation issues on the frontend.
If these steps do not resolve the 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. Should the problem persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to translate the VAT label in the WooCommerce checkout using WPML. Although the translations are available in the string translation section and are translated, they do not appear on the checkout page. Solution: First, apply the workaround described on the errata page for issues related to missing translations due to WordPress 6.7 MO files not being loaded. You can find the details here: WordPress 6.7 MO files not loaded. Next, ensure that your theme and any plugins related to the VAT string are properly scanned for translations. This can be done under WPML -> Theme and plugins localization. Then, enable auto-registering of strings as described in this guide: Finding strings that don't appear on the string translation page. Finally, use the WPML String Translation to translate all instances of the VAT string.
If this solution does not resolve your issue, or if it 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: You are using WPML to translate content on your site, but while translations are available, they are not visible on the frontend. Solution: First, ensure that the WPML String Translation can write in the necessary folder. This issue might be due to insufficient writing permissions. Contact your hosting provider to adjust these permissions as outlined here: WordPress File Permissions. After resolving the permissions issue, apply the workaround provided on the WPML errata page here: WordPress 6.7 .mo files not loaded and verify if the translations now appear on the frontend.
If this solution does not resolve your issue or seems outdated, we highly recommend checking related known issues at WPML 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.
Problema: Il cliente sta cercando di tradurre i pulsanti come 'Find Events', 'Today' e 'Subscribe to Calendar' nelle sezioni generate dal plugin 'The Events Calendar' utilizzando Elementor con il tema Hello. Nonostante abbia configurato alcune opzioni nella sezione di WPML 'Localizzazione di temi e plugin', non riesce a tradurre questi elementi. Soluzione: I pulsanti menzionati dovrebbero essere tradotti tramite la funzione Traduzione Stringhe di WPML. Tuttavia, se il contenuto non appare tradotto, potrebbe essere dovuto a un bug noto di WordPress. Consigliamo di consultare la pagina dei problemi noti di WPML per ulteriori dettagli su questo bug: Missing translations on front-end.
Se la soluzione proposta non risolve il problema o se le informazioni risultano obsolete, ti invitiamo a aprire un nuovo ticket di supporto. Ti consigliamo vivamente di verificare i problemi noti correlati, di controllare la versione della correzione permanente e di confermare che hai installato le ultime versioni dei temi e dei plugin. Per assistenza ulteriore, visita il forum di supporto WPML.
Problem: If you're experiencing issues with WPML where automatic translations are stuck in the queue, it might be due to plugin conflicts or incorrect settings. Solution: First, ensure that your 'Views' post type is set to 'Not Translatable' in 'WPML > Settings > Post Type Translation'. This setting is crucial as having 'Views' translatable can cause issues with automatic translations. Next, check for any plugin conflicts. Specifically, the 'WP External Links' plugin has been known to interfere with the translation process. Try deactivating this plugin to see if it resolves the issue. If the problem persists, you might need to clear the translation queue and reset the translation settings:
Navigate to 'WPML > Support > Troubleshooting'
Click on 'Cancel in-progress automatic jobs'
Clear the cache in WPML
Fix element_type collation
Synchronize local job ids with ATE jobs
Synchronize translators and translation managers with ATE
Assign translation status to duplicated content
Set language information
Fix post-type assignment for translations
After these steps, switch the translation mode back to 'Translate Everything Automatically' under 'WPML > Settings'. If these steps do not resolve the issue, it may be necessary to provide temporary access to your site for further diagnosis. Remember to back up your site before making any changes.
Please note that this solution 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 problem persists, please open a new support ticket at WPML support forum.
Problema: O cliente estava enfrentando problemas com o plugin WPML após remover o GTranslate. O WPML parou de funcionar corretamente, apresentando uma mensagem de erro indicando um problema com algumas tabelas no banco de dados, especificamente a tabela 'cobaia_wp102.wp_icl_strings' que não existia. Além disso, após a remoção do GTranslate, as páginas duplicadas permaneceram e as traduções não estavam aparecendo corretamente.
Solução: Primeiramente, solicitamos acesso ao site do cliente (WP Admin e FTP) para poder identificar e resolver o problema. Verificamos que o problema estava sendo causado por regras específicas no arquivo .htaccess que foram adicionadas pelo GTranslate. Removemos essas regras do arquivo .htaccess, o que resolveu o problema com as traduções não aparecendo corretamente. Pedimos ao cliente para confirmar se a página inicial em alemão estava funcionando como esperado após a remoção dessas regras.
Se esta solução não resolver o seu problema ou se ela parecer desatualizada, recomendamos que abra um novo ticket de suporte. Também é altamente recomendável verificar os problemas conhecidos, verificar a versão da correção permanente e confirmar que você instalou as versões mais recentes dos temas e plugins.
Problem: The client was using the Premium Addons for Elementor widget for their blog, along with WPML for translation. They encountered an issue where the category filter worked correctly in Estonian, the main language, but displayed Estonian posts when filtering in English. Solution: We recommended reviewing an errata our team published, which addresses issues with the Premium Addons for Elementor Widget not displaying posts in secondary languages when including or excluding post categories. You can find the errata here: https://wpml.org/errata/premium-addons-for-elementor-blog-widget-not-showing-posts-in-the-secondary-language/ We also suggested updating the Hello Elementor theme, Premium Addons for Elementor, and Elementor itself. After updates, it was necessary to re-add the snippet from the errata to the functions.php file.
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.
Problem: The client is experiencing issues with the synchronization of translations when reordering Flexible Content Layout Blocks in a site built with ACF Pro and WPML. This causes the content in translated pages to go out of order, even though the headings remain unchanged. Solution: We recommend the following steps to address the issue: 1. Make a full backup of your website. 2. Delete the translations of the affected pages by visiting the Pages tab, switching to a secondary language, and sending the translation to the trash. Then, permanently delete the post from the trash for all secondary languages. 3. Go to WPML > Settings > Translation Editor and adjust settings as needed. 4. Make a small change to the default language post (e.g., add a blank space to a custom field text). This step is crucial as it invalidates the current translation job and forces WPML to create a new one with the correct Repeater fields order, as described in the errata.
If this solution does not resolve your issue, or if it 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 problems persist, please open a new support ticket.
