Problem: You merged your staging website to the live site and encountered an issue where WPML is stuck in an infinite loop asking for a migration code, which you cannot obtain because the link redirects you back to the 'new address detected' message. Additionally, the new version of WPML is not showing up in the production channel. Solution: First, when the message 'new address detected' appears, click 'yes, this is a copy'. For the subsequent question about sharing translation credits, click 'No'. Next, please visit your WPML account dashboard at https://wpml.org/account/sites/ and create a new sitekey for your domain. Then, in your website backend, navigate to WP > Plugins > Add new > Commercial Tab, click on 'Unregister this sitekey', and replace the sitekey with the new one. 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: After duplicating and translating an article, the translated version is not displayed on the website. The client lost the previous chat with support. Solution: We found that in the
wp_options
table, two keys were empty:
wpml.ate_sync.lock
and
wpml.ate_sync.lock.key
. Deleting these keys allowed WPML to repopulate them, resolving the issue. We recommend you check these keys in your database and delete them if they are empty to see if this resolves the issue for you as well.
If this solution does not apply to your case, or if it seems outdated, please open 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 contact us through the WPML support forum.
Problema: Stai cercando di completare la traduzione di una pagina, ma arrivi al 95% e l'ultima stringa non viene salvata. La frase originale ha dei marcatori di formattazione incorporati (un marcatore di formattazione all'interno di un altro marcatore di formattazione), e i marcatori di formattazione nella traduzione non sono incorporati correttamente. Soluzione: Se stai riscontrando questo problema, ti consigliamo di passare alla versione precedente dell'editor di traduzione. Puoi farlo dalle impostazioni in alto a destra dell'editor.
Questa soluzione potrebbe non essere più rilevante a causa di aggiornamenti software o potrebbe non applicarsi al tuo caso specifico. Se il problema persiste, ti invitiamo a consultare la pagina dei problemi noti per verificare se è già stata trovata una soluzione. Assicurati inoltre di avere installato le ultime versioni dei temi e dei plugin. Se necessario, apri un nuovo ticket di supporto sul forum di supporto WPML.
Problem: You are trying to translate pages using Avada Builder, but not all parts of the page are translated. Solution: First, ensure that the text you are trying to translate appears in the translation editor.
Here are the steps we recommend: 1. Make a slight modification to the original page and save it. This action can help refresh the page translation. 2. Navigate to the WPML translation editor to see if the changes are reflected and the missing content appears for translation. 3. Verify that you are using the latest version of your theme, as outdated themes can sometimes cause issues with translation plugins.
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 for further assistance.
Problem: You are trying to translate pages using Avada Builder, but not all parts of the page are translated. Solution: First, ensure that the text you are trying to translate appears in the translation editor.
Here are the steps we recommend: 1. Make a slight modification to the original page and save it. This action can help refresh the page translation. 2. Navigate to the WPML translation editor to see if the changes are reflected and the missing content appears for translation. 3. Verify that you are using the latest version of your theme, as outdated themes can sometimes cause issues with translation plugins.
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 for further assistance.
Problem: The client is experiencing an error when translating their website from English to Czech, stating that 'The following target languages do not support automatic translations: English UK. To enable automatic translation map them to known languages.' Solution: We recommend ensuring that the language used is correctly mapped to a recognized language. It appears that the client might be using a custom-modified language with a UK locale. To resolve this issue, please map this language to English as described in our guide on Editing WPML’s Languages Table, specifically looking at the 'Language Mapping' field.
If this solution does not apply because it might be outdated or not relevant 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 issues persist, please open a new support ticket.
Problem: You are developing a site and need to choose a translation method for WPML among Google, Azure, or WPML itself, considering different pricing options. You are also concerned about what happens if your translation credits run out during the process. Solution: We recommend assigning your prepaid credits first and using them before switching to a pay-as-you-go model, as prepaid credits cannot be used with pay-as-you-go. For more details, please visit https://wpml.org/forums/topic/how-to-assign-prepaid-credits-to-a-pay-as-you-go-site/#post-13668311. If cost is a significant factor and you do not have specific quality expectations, using Azure might be a cheaper and more appropriate option. However, if you seek top-quality translations, be prepared for higher costs. We suggest running tests in small batches with different translation engines to determine which one meets your satisfaction.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client has completed translations for pages using the translation editor, and these are registered as completed in the Translations panel. However, the translations are not displaying on the frontend. The client recently switched from using Bakery builder to Elementor Pro and updated to the Hello Elementor child theme. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Edit the page in the default language. 2. Add "V2" to the title and update the page. 3. Delete the "V2" from the title and update the page again. 4. Update the page's translation. After completing these steps, please check if the translated page is now visible on the frontend.
This solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
