Problem: You are trying to delete and reinstall WPML after a problematic migration from development to production, but you encounter an error message saying 'Sorry, you are not allowed to access this page' when following the reset instructions. Solution: This issue might be related to the migration process. We recommend the following steps to manually clean up your database: 1. Access your database. 2. Delete all tables that start with
1
wp_icl_
. 3. Go to the
1
wp_options
table and run these SQL queries to select and then delete the relevant entries:
1
SELECT * FROM `wp_options` WHERE `option_name` LIKE '%icl%'LIMIT 50
1
SELECT * FROM `wp_options` WHERE `option_name` LIKE '%wpml%'LIMIT 50
4. After cleaning the database, reactivate WPML and set it up again. Ensure you back up your database before making any 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate a product page using WPML and Elementor, but after translating, the 'Description' section is overwritten by the original Greek language instead of retaining the English translation. Solution: 1. Ensure you perform a full backup of your site. 2. Update all WPML and Elementor plugins to their latest versions. 3. Go to the primary language version of the product and resave it. 4. Retranslate the product to English. If the issue persists after following these steps, it might be due to an outdated solution or a different underlying problem. We 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that some blocks appeared correctly on the frontend but looked empty in the "edit page" view. Solution: We resolved the issue by performing several troubleshooting steps in WPML > Support > Troubleshooting. Here are the steps we recommend you try: 1. Remove ghost entries from the translation tables 2. Fix element_type collation 3. Fix WPML tables collation 4. Set language information 5. Fix post type assignment for translations After completing these steps, please resave your Global language page and retranslate it. This should copy the selected fields to the translated language. Ensure you back up your data before proceeding.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client is unable to translate the EAN number for the Dutch version of a WooCommerce product using WPML. Solution: We configured the "_alg_ean" custom field to copy the EAN to translations. To apply this change, follow these steps: 1. Navigate to Products -> All Products in your WordPress dashboard. 2. Ensure you are viewing the default language. 3. Select all products displayed on the page. 4. Choose 'Edit' from the bulk actions menu. 5. Change the status to 'Published' or modify any other field that does not impact your products significantly. 6. Click 'Update' to save the changes. After completing these steps, please verify if the EAN numbers are correctly copied to the translated products.
If this solution does not resolve your issue or seems outdated, we recommend checking the related known issues 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 is using WPML for the first time to translate products from Slovenian to Croatian and is unsure how to automatically translate categories and their descriptions before translating the products. Additionally, the client is facing issues with the word count for translations being higher than expected, leading to a shortage of translation credits. Solution: We recommend translating categories automatically along with the products. After translating the products, you can synchronize the taxonomies at WPML > Taxonomy Translation. If you prefer to translate all categories in one step, you could assign all categories to one product and send this product for automatic translation. For syncing issues, a sync button will appear at the bottom of the section inside WPML > Taxonomies Translation when selecting a taxonomy to translate.
For importing existing translations, use the "WPML Export & Import" addon instead of the outdated "WPML All Import". You can download this addon under Plugins > Add new on the "Commercial" tab. Ensure to first import categories before posts if you're also importing categories. Guide: https://wpml.org/documentation/related-projects/wpml-export-and-import/
Regarding the word count issue, our development team is aware and working on a solution. The estimated word count might be 2-3 times higher than expected due to the current bug.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if problems persist. For further assistance, visit our support forum: https://wpml.org/forums/forum/english-support/
Problem: The client reported that after manually translating the 'About Us' page to Spanish, the content reverted to English within a few hours. Additionally, a critical error occurred preventing the page from loading. Solution: We first suggested ensuring that manual translations are edited manually. Upon further investigation, we discovered a critical error unrelated to WPML, indicated by a fatal error due to memory exhaustion. We recommended: 1. Checking the server error logs, which can be done by following the debugging guide at https://wpml.org/documentation/support/debugging-wpml/ 2. Consulting with the hosting provider to address the memory limit issue.
If this solution does not resolve your issue, or if it 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 problems persist, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues accessing the Translation management page on your staging site. The page appears blank, and you receive a message indicating that the site seems to have moved, although the URLs are the same. Additionally, there is an error in the admin bar about needing to map languages, but no languages are loaded for mapping. Solution: We resolved the issue by setting the site as a copy, which made the Translation management page available again. To connect your sites and share translation memory and credits, we recommend following the steps outlined in our documentation on Automatic Translation Subscription for Multiple Sites.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. For further assistance, you can also visit our support forum at WPML Support Forum.
Problema: Estás intentando actualizar la página 'Animales en el refugio' en inglés y traducir la página 'Cuervo grande' en WPML, pero enfrentas problemas. Además, Google detecta contenido duplicado en el sitemap de varios subdominios, lo que te llevó a seleccionar la opción 'Duplicar'. Solución: Cuando duplicas una página en WPML, se copia todo, incluyendo el título SEO y las descripciones, desde el idioma principal. Para resolver esto, debes editar la página secundaria y hacer clic en el botón
Si esta solución no resuelve tu problema o si la información parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: You are running a scan using Wordfence and encountered an issue with the Sticky Links plugin, which appears to be outdated and potentially incompatible with the current version of WordPress. Solution: We are aware of the warning issued by Wordfence regarding the Sticky Links plugin. You can safely ignore this warning for now as you can still use the plugin without any issues. However, if you encounter any problems with this or any other WPML plugins, we recommend you contact us.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: Sie haben festgestellt, dass sich Texte in Ihrer Quellsprache auf der gesamten Website geändert haben, aber nur in Elementor und nur im Output. Die Texte erscheinen in der Elementor-Seitenleiste unverändert, ändern sich jedoch auf der Seite selbst. Solution: Dies ist ein bekanntes Problem. Wir empfehlen Ihnen, die folgende Problemumgehung zu versuchen: https://wpml.org/errata/elementor-strings-registered-as-a-widget-strings-in-wpml-string-translation/
Falls diese Lösung für Sie nicht relevant ist, weil sie veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen Ihnen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: https://wpml.org/de/forums/forum/support-in-german/
Problem: You want to assign prepaid credits to your website, but it is not listed in the manage credits section. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to Plugins → Add New and click the Commercial tab. If you see an 'Unregister WPML from this site' button, click it. If not, proceed to the next step. 2. After the page loads, click on 'Register WPML'. You will see a message asking you to enter the site key. Click on 'Get a key for this site'. 3. Complete the site key wizard in your WPML account. 4. Copy your new key and paste it in the Commercial tab. Then, delete your old site key in your WPML account. 5. Now, you should be able to assign the credits to your site.
Please note that 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.
Problem: The client was unable to see the language switcher options on their live site, although they were visible when logged into the CMS. The issue was identified as custom CSS hiding the language switcher. Solution: 1. We confirmed that the hiding of the language switcher was due to custom CSS, which is not added by WPML by default. We suggested checking the site to identify where this CSS is coming from and remove it. 2. We recommended increasing the WP Memory Limit to at least 128MB for WPML to function properly, as the current setting was only 40MB. This involves adding the following lines to the wp-config.php file:
3. We advised updating to the latest version of WPML (4.7.3) to ensure compatibility and functionality. 4. If the problem persists, we suggested providing temporary access to the site for further investigation and possibly needing permission to deactivate/reactivate plugins and themes for troubleshooting.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client was updating their website when they encountered a conflict between WPML and BetterDocs Pro, causing the website to stop functioning. Solution: We identified that the error originates directly within the BetterDocs Pro plugin. We recommend updating all WPML plugins to the latest version, specifically to version 4.7.3, as this may resolve the issue. If the problem persists after updating, we advise contacting the developer of BetterDocs Pro, as they might already have a solution to this error. Please let us know the outcome.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please open a new support ticket at WPML support forum.
The client was experiencing issues with broken CSS on their multilingual site pages using the Bricks theme. The CSS conflicts occurred because the Bricks theme custom fields were set as 'Don't translate', preventing styles and alignment preferences from being copied to secondary language pages.
Solution:
We resolved the issue by adjusting the WPML settings to ensure that the Bricks theme custom fields are copied to translations:
1) Navigate to WPML>>Settings>>Custom Fields Translation. 2) Click on the Show system fields link. 3) Search for 'bricks' fields. 4) Select the Copy option for these fields and save the changes. 5) Open the Contact page for editing in Romanian and update the page. 6) Update the English translation of the Contact page. 7) Repeat steps 5 and 6 for the Order page.
We recommend clearing your site's caches after these changes.
If the issue persists or if this solution becomes outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You need to export product attributes and their translations into a single table using SQL or the WP ALL EXPORT plugin, but currently, they export as separate rows. Solution: We tested the WP All Export Pro and WP All Export - WooCommerce Export Add-On Pro plugins and found that each translation has a separate Term ID, causing each term to start on a new line in the export file. To organize the data in a single table, you can add the custom fields _wpml_import_language_code and _wpml_import_translation_group. After adding these fields, sort your spreadsheet based on _wpml_import_translation_group to group the English term with its translations. Additionally, consider using AI to reorganize the spreadsheet if necessary, as it might be simpler than custom coding.
If this solution does not apply to your case, or if it 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 you still need assistance, please open a new support ticket at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
