Problem: The client is experiencing issues with SSL validation for different language domains using WPML and SAM SSL. Initially, all domains were validated, but now they face intermittent validation failures, with error messages about security in incognito mode. Solution: 1. We recommend following the steps outlined in our guide on setting up different domains per language, which can be found here: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/. It's possible that the validation message is a false positive. Try unchecking the validation checkboxes, save the settings, and then test your domains again. 2. Update your WPML plugin to the latest version (4.6.11) and all related add-ons. This update includes bug fixes and improvements that might help resolve your issue. Update instructions can be found here: http://wpml.org/faq/install-wpml/. Make sure to back up your database before making any changes.
If these steps do not resolve the issue, or if the solution provided here becomes outdated or seems 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that after activating the WPML Multilingual CMS, the search preview functionality provided by the 'FiboSearch - AJAX Search for WooCommerce' plugin stopped working on their live site, although it worked fine on the staging site. Solution: We recommended that after activating the WPML plugin, the client should navigate to WooCommerce > FiboSearch > Indexer and click on 'Rebuild Index'. This action should restore the search form's functionality in the frontend.
If this solution does not resolve the 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. Should further assistance be needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues with string translation for all products on your website after support intervention. Solution: To resolve the string translation issue for all products, follow these steps: 1. Edit the template in the original language and make a small change, such as adding a space after the button text. This triggers the update so that it will show in the Advanced Translation Editor. You can remove the space afterward. 2. Open the Advanced Translation Editor. You should see the original text and the English translation filled in. Click the green checkbox to accept this translation. Remember to clear the cache to ensure the changes reflect on the frontend immediately.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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.
Problem: The client reported that the filter "Marine Speakers and Subwoofers" was not functioning on their WooCommerce site. Additionally, they mentioned that the "annasta Woocommerce Product Filters" plugin was not working at all. Solution: We acknowledged a misunderstanding due to a name change of a plugin from WOOF to HUSKY, which was still listed under its old name in our compatibility list. The client resolved the filter issue by renaming their category and updating the URL slug, which made everything work perfectly. For future issues or questions, we advised the client to open a new support ticket.
Please note that this solution 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to use the 51,000 credits assigned for translations directly from the WPML backend, but the WPML backend only shows the option 'Activate pay-as-you-go and continue', preventing the use of the assigned credits. Solution: We have reviewed your issue and noticed that your 51,000 credits are assigned to a key that is not registered with your website. Please follow these steps: 1. Delete the site key on wpml.org. 2. Create a new key and register your site. 3. Then assign those credits again.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 WPML support forum.
Problem: The client is using the Astra theme with WooCommerce and WPML for a multilingual site with English and German languages on separate domains. The 'Slide In Cart' feature works in English but not in German; instead of sliding in, the page reloads. Solution: We recommend the following steps to address the issue: 1. Navigate to the folder
with the updated version available. 3. After replacing the file, check the functionality of the problematic products on the front end.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your 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 visit our support forum at WPML Support Forum.
Problem: The client is facing an issue with translating custom taxonomy terms "tags_media" and "categorie_media" associated with attachments while transitioning their website into a multilingual platform using WPML. Although the terms are translated and registered on the original images in French, their translations do not appear for the translated media items. Solution: If you're experiencing this issue, we recommend you try the following steps: - Navigate to WPML > Support > Troubleshooting. - Click on the following buttons: -- Synchronize posts taxonomies [Select 'Media' from the Dropdown list before clicking this button] -- Clear the cache in WPML -- Assign translation status to duplicated content -- Set language information -- Fix terms count -- Fix post-type assignment for translations - After completing these steps, open any of the default posts in the Editor. - Add an image with an associated taxonomy, save the changes, and then update the translation.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 has a custom post type called Recipes. After duplicating and translating these posts using WP All Import, updating the original English Recipes also reverted the translations back to English. This issue likely arose because the posts were duplicated instead of being set to translate independently. Solution: To prevent this issue, it's recommended to set posts to be translated independently, so updates to the original language don't affect the translations. Unfortunately, there's no option to change all posts to 'translated independently' at once; this adjustment needs to be made in the database. You can use a tool like phpMyAdmin to access your database. In the
wp_postmeta
table, you should delete the key
_icl_lang_duplicate_of
for the duplicated posts. This action can be performed in bulk with the correct SQL query. However, directly modifying the database can be risky. Ensure you have a full backup before proceeding.
For more details on translating sites built with ACF, you can visit this link.
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 issues persist, please open a new support ticket.
Problem: The client reported that the 'underlined-link' class attribute present in the English version of a webpage was missing in the translated Hungarian version, despite attempts to re-translate after making changes to the original. Solution: We recommended that the client check the WPML and Bricks settings on their site against those on a clean installation where the issue was not replicated. We provided a sandbox link for reference. The client was advised to create a test page, translate it, and check if the issue persists. If the problem is still reproducible, we asked the client to inform us on how to replicate it so we could further investigate with our compatibility team.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to translate pages, but the translation status refresh never finishes and keeps loading. Solution: 1. Enable a minimal environment by deactivating all non-WPML plugins and switching to a standard WordPress theme. Remember to back up your database and website before proceeding. 2. If the problem persists, navigate to WPML > Support > Advanced Translation Editor and share screenshots of the recent error logs. 3. Check the PHP setting for max execution time. If it's low, increase it by adding the following code to your
wp-config.php
file:
set_time_limit(300);
This adjustment should help complete the translation. For more details, visit WPML documentation.
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 needed.
Problem: If you're experiencing issues with the order of images in translated posts not matching the original, or if the feature image section appears incorrect, follow these steps to resolve the issue. Solution: 1. Navigate to WPML > Settings > Media Translation and enable all options except "Translate media library texts with posts". 2. Edit the post in the original language (English), make a small change, save, and then update the translation. 3. Switch to the Greek language and publish the translated post. If some translation images are broken, delete all images in the Greek language and re-update the post in English. For issues specifically with the photo order in galleries created by ACF and the theme Kalium, install the ACF Multilingual plugin, update the post in English, and then update the translation. This should correct the photo order in the frontend. Refer to the documentation on translating sites built with ACF.
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 needed, please open a new support ticket at WPML support forum.
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: 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.
