Problem: The client has a license for a website and set up a staging site using a different domain. They encountered issues updating WPML Multilingual CMS and Advanced Custom Fields Multilingual due to the domain change. Solution: If you're experiencing this issue, we recommend using a separate license for your staging site. You can generate a new WPML key by visiting your WPML account, then unregister the old key if necessary, and register with the new key under Plugins > Add New > Commercial.
For updating the plugins manually, follow these steps:
Create a full website backup.
Download the latest version of WPML and any other WPML add-ons from WPML Downloads.
Disable and delete the current WPML Multilingual CMS plugin (note: settings and translations are saved in the database and will not be deleted).
Upload and activate the freshly downloaded WPML plugin from Plugins → Add New → Upload Plugin → Activate WPML.
Repeat the process for the Advanced Custom Fields Multilingual plugin as well.
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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: The client reported that some translations previously entered into the Advanced Translation Editor (ATE) were missing, even though the translated content was still correctly displayed on the live website. This issue occurred after updating WordPress and plugins.
Solution: We suggested that the issue might have arisen because the original text was altered or edited, causing ATE to recognize it as different text. As a result, the client would need to re-enter the translations. Additionally, the client mentioned that they restored a backup from before the updates, which resolved the issue temporarily. We advised that if the problem reoccurs after future updates, the client should contact us again.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're experiencing similar issues, we 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 the problem persists, please open a new support ticket with us for further assistance.
Problema: O cliente relatou que o alternador de idioma no menu funcionava apenas na página inicial e no idioma principal quando não estava logado ou em modo anônimo. Em outras páginas, o alternador não mostrava as opções de outros idiomas. Solução: Verificamos o problema e identificamos que o jQuery não estava carregando corretamente, o que afetava o menu dropdown do alternador de idiomas. Observamos também erros relacionados ao cache e arquivos JS minificados. A solução foi recriar os arquivos de cache e os arquivos minificados utilizando o plugin WP Rocket. Após essa ação, o seletor de idiomas passou a funcionar corretamente em todas as páginas e em modo anônimo. Pedimos que o cliente teste novamente e confirme se o problema foi resolvido.
Lembre-se de que esta solução pode não ser relevante para o seu caso, pois pode estar desatualizada ou não se aplicar à sua situação específica. Se o problema persistir, 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 de temas e plugins.
Problem: The client was experiencing an issue where HTML code within an Elementor Pro HTML widget was appearing on the translation page, and the client was being forced to translate it. Solution: We recommended moving the code from the Elementor HTML widget to the
functions.php
file of the client's Child Theme. We provided the following code to correctly add JavaScript to the theme, which prevents the Advanced Translation Editor (ATE) from confusing HTML and script code:
After applying this change, the English version should display correctly and execute the JavaScript code without it appearing in the translation editor.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket in our support forum.
