Problem: You are trying to import posts in English and Greek using WPML, WPML All Import, and WP All Import. Despite having all necessary plugins installed and activated, the WPML All Import option is not visible in the WP All Import Setup wizard (step 3). You have already tried increasing the memory limit, updating WP Core and PHP version, re-registering WPML, and reinstalling WPML All Import. Solution: The issue might be due to the WP All Import plugin folder not having the default name, which should be
wp-all-import-pro
. We recommend checking the folder name and renaming it to the default if necessary. This should make the WPML All Import option appear correctly in step 3 of the WP All Import Setup wizard.
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, 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 the problem persists. You can do so at WPML support forum.
Problem: The client needed guidance on how to translate a specific page and apply the same translation process to similar posts. Solution: We recommended following our detailed documentation on translating custom post types. You can find the guide here: Translating Custom Posts.
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 do not hesitate to open a new support ticket or visit our support forum at WPML Support Forum.
Problem: You are experiencing an issue where links on old pages, which are part of joined segments, stop working in the frontend. These links incorrectly redirect to the same page, displaying an empty href attribute, although they appear correct in ATE. This problem does not occur with newly created pages. Solution: We recommend trying the "Translate Link Targets" option in WPML → Settings. This might resolve the issue with the links in the frontend. Please ensure to backup your database before making any changes.
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 the issue persists, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: The client is trying to set the English version of a product to 'Published' and the Dutch version to 'Draft'. However, changing the status of the Dutch product to 'Draft' also changes the English product to 'Draft'. Solution: We recommend the following steps to manage the status of products in different languages independently: 1. Navigate to Products, switch to the translation language, edit the product, and manually set its status to 'Draft'. This should work as long as the translation is not marked as a duplicate. 2. Alternatively, go to WPML -> Settings -> Translated documents options and set it to 'Save the translated post as a draft'. This setting will automatically save all new translations as drafts, and you will need to manually update them to 'Published' if needed. If you are using any WPML add-on or another plugin that might be syncing the status of posts, consider testing with all non-WPML plugins deactivated on a staging site to identify any conflicts.
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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: El cliente tiene problemas con la traducción incorrecta de la palabra "productos" en la página de la tienda en francés, donde aparece como "produit" en lugar de "produits". Solution: Si estás experimentando este mismo problema, te recomendamos que verifiques la traducción en el tema de Porto, que utiliza el text-domain de WooCommerce. Busca la cadena "%s products" y asegúrate de que esté traducida correctamente a "%s produits" en francés. Puedes hacer esto a través de la herramienta de traducción de cadenas de WPML.
Si esta solución no resuelve tu problema, o si parece estar desactualizada o no aplicable a tu caso, te sugerimos abrir un nuevo ticket de soporte. También te recomendamos revisar los problemas conocidos relacionados, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problem: You are unable to find a way to modify or eliminate the WPML Switch at the bottom of the website. Additionally, you are looking for a method to only showcase the language that is not active. Solution: We recommend customizing or removing the footer language switcher by navigating to WPML → Languages → Footer language switcher settings. For more information on how to set up your language switcher, please visit: Language Switcher Options.
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 do not hesitate to open a new support ticket at WPML Support Forum.
Problem: When attempting to create a new KO translation from an English page after deleting the previous KO page, a critical error occurs, preventing further actions. Solution: First, ensure that all WPML plugins are up to date. If the problem persists, enable the debug log to identify the underlying issue. To do this: 1. Open your
wp-config.php
file. 2. Locate the line
define('WP_DEBUG', false);
and change it to:
define('WP_DEBUG', true);
3. Add another line to enable error logging to a file on the server:
If these steps do not resolve the issue, it may be due to an outdated solution or a different 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 the problem persists, please open a new support ticket with us for further assistance.
Problem: The client reported issues with duplicate queries and missing translations in a multilingual WordPress setup using WPML and WooCommerce Multilingual (WCML). They also inquired about setting up a fallback option for untranslated products and categories. Solution: 1. We recommended deactivating WPML and WCML to check if the duplicate queries persist. After running WPML troubleshooting actions from WPML->Support->Troubleshooting, we identified that the remaining queries were not related to WPML. 2. For the fallback option, it can be enabled from WPML->Settings->Post Types Translation -> Translatable use translation if available or fallback to default language. We provided a link to our documentation for further guidance: documentation. 3. To address the issue of missing translations for product categories, we suggested setting certain taxonomies to "Translatable - only show translated items" from WPML -> Settings -> Taxonomies Translation.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, you can also visit our support forum at WPML support forum.
Problem: After the client's hosting was temporarily deactivated during a renewal, WPML on their site started showing a 'new address detected' notification, even though the address had not changed. Solution: We suspect that the temporary deactivation of the hosting might have triggered this notification. If you're experiencing this, we recommend selecting the option in the WPML notification that indicates your site has a new location. This might resolve the issue.
If this solution does not work or seems irrelevant because it might be 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 problem persists, please open a new support ticket.
Problem: The client is experiencing issues with their staging site after cloning their production site using the Plesk administration interface. The URLs for the WordPress Address (Site URL) and Site Address (Home URL) are not correctly set after the migration, which is suspected to be managed by WPML. Solution: We recommend checking the settings in WordPress under Settings → General to ensure that the WordPress Address (Site URL) and Site Address (Home URL) are correctly set. WPML reads these values from the wp_options table and does not alter them. If these values are correct, WPML should function properly. It's important to verify that the entire database, including the wp_options table, has been correctly migrated to the staging site.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific case, we highly recommend opening a new support ticket. Additionally, 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. For further assistance, you can also contact us directly at the WPML support forum.
Problem: The client is trying to translate a custom post archive created with ACF from German to English, specifically from 'leistung' to 'service'. However, when attempting to edit the slug in the Archive Settings in ACF, it also changes the German slug. Solution: We recommend going to WPML > Settings > Taxonomies Translation and setting your custom taxonomy to "Translatable - only show translated items." Next, enable WPML > Settings > Slug translations and translate the slug accordingly. If this does not resolve the issue, it might be because the solution is 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 for further assistance.
Problem: The client reported that the WordPress UI is set to English, and all WordPress settings are in English, but Elementor still loads in Norwegian when WPML is installed. The client was concerned about WPML creating unnecessary translation files and using translation credits for UI elements. Solution: We clarified that the JSON/PHP files seen by the client are added by WordPress, not WPML. You may try to follow the steps from this thread to see if this resolves the issue: https://wpml.org/forums/topic/elementor-editor-interface-with-wpml/#post-9863547
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.
Problem: The client is using the Listeo theme and has encountered an issue where custom fields such as description, address, spot on map, phone, and contact email are not visible on the translation page or the listing page when using WPML to translate from Greek to English. Solution: We recommend making the custom fields translatable. You can do this by navigating to WPML > Settings > Custom fields translation > Show system fields and setting the necessary fields to 'translatable' or 'copy', depending on the field. This process may require some trial and error to identify the correct fields. For a detailed guide on translating custom fields, please visit https://wpml.org/documentation/getting-started-guide/translating-custom-fields/.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where WPML does not translate the homepage correctly from Greek to Romanian. Only the header part of the page is translated. Solution: We reviewed the issue and found that adding a space to the title resolved the problem, making the translation appear correctly. If you're experiencing a similar issue, we recommend checking the title for any formatting errors and adjusting it accordingly.
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.
Problem: You are trying to translate a section of your theme related to room facilities, but while the text translates, the images do not appear in the translated version. Solution: This issue occurs because the icons for the room facilities are not defined in the specific language you are translating to. For instance, if the icons are visible in the English version, you need to ensure they are also set up for other languages. You can do this by navigating to the Room Facility options in your WordPress admin panel and selecting the appropriate language from the top bar. Once there, you need to define the icons for each facility by clicking on "Choose an Icon".
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current setup, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum 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