The client is unable to access the 'Translations queue' to review translations before publishing. The page shows a 'loading' circle and does not load the translated content. Additionally, the client encounters several error and deprecated notices related to WordPress functions.
Solution:
We recommend following these steps to resolve the issue:
1) Create a new post for testing. 2) Navigate to WPML>>Translation Management Dashboard. 3) Select the post for translation or update existing translations. 4) Send it to the Translation Basket. 5) Go to WPML>>Translation Management>>Translation Basket. 6) Assign yourself as the translator and send it for translation. 7) Visit WPML>>Translations queue and translate the post by clicking the 'Translate' button.
If the issue persists, try removing yourself from the translators list and then re-adding yourself:
1) Go to WPML>>Translation Management. 2) Click on the 'Translators' tab. 3) Remove yourself from the translators list. 4) Refresh the page. 5) Revisit WPML>>Translation Management>>Translators. 6) Add yourself back as a translator.
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.
Problema: Stai cercando di inserire le bandierine della doppia lingua (italiano - inglese) nel menu del tuo sito, ma riscontri un errore di visualizzazione. Soluzione: Il problema deriva dal tema Salient. Ecco due possibili soluzioni: 1. Nella sezione Salient > Header Navigation > Animation Effects, scegli un effetto diverso da "Text reveal". 2. Modifica il codice nel seguente modo:
Nota che questa modifica dovrà essere riapplicata ad ogni aggiornamento del tema finché non verrà corretta dall'autore.
Se questa soluzione non risolve il problema o se sembra non essere più rilevante, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di consultare la pagina dei problemi noti, verificare la versione della correzione permanente e confermare che hai installato le ultime versioni dei temi e dei plugin.
The client is experiencing an error message 'Unable to register: Site key not matching' when attempting to register their site with WPML using a generated site key.
Solution:
1. Visit https://wpml.org/account/sites/ 2. If the site URL is already registered, delete it from the list. 3. Re-enter the site URL to generate a new site key. 4. Click on "Show key" and copy the new site key. 5. Navigate to Plugins > Install > Commercial (tab) and enter the new key to re-register WPML. If WPML is still registered, de-register it first.
If you're experiencing this issue, we recommend following these steps to resolve it. However, 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.
Problem: The client wants data entered in the main language (FR) for ACF repeater fields to be automatically copied to other languages (EN, NL, DE) without the possibility of modification. Despite having set the fields to 'Copy' in WPML's 'expert mode', some repeater fields are still editable in other languages, and changes in FR are not reflected in other languages. Solution: We found that the issue was due to incorrect settings for the ACF repeater fields. Only the 'bungalows_semaine' field was set to 'copy', while the other fields were not. After adjusting the settings to 'copy' for all relevant fields and using the translation editor to translate a draft page, the fields were successfully locked and copied from the original. It's crucial to use the translation editor for WPML to apply the ACF translation preferences correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 at https://wpml.org/forums/.
If you're experiencing issues editing investment pages on your site using WPML, and encountering an error due to a compatibility conflict with JetEngine when manually translating the Post Type.
Solution:
We recommend trying the following steps as a temporary workaround after ensuring you have a full site backup:
1) Navigate to WPML>>Settings. 2) Scroll down to the Slug translations section. 3) Uncheck the Translate custom post and taxonomy base slugs (via WPML String Translation) option. 4) Save the changes.
Alternatively, you can: - Go to JetEngine>>Post Types. - Edit your Custom Post Type (Investments). - Go to Advanced Settings. - Disable the "Show in Rest API" option. - Save the changes.
If this solution does not resolve your issue or seems irrelevant due to being 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. If needed, please open a new support ticket at WPML support forum.
