Problem: The client is using WPML with WP All Import to update product information nightly. While the product images for the default language (NL) are refreshing correctly, the German (DE) product images are not updating and still display the old images. The client has tried using the image/media sync feature in WPML without success.
Solution: 1. We recommended ensuring that the 'Duplicate uploaded media to translations' option is selected for the product in the original language. This can be done by editing the product and checking the option.
2. We also set the custom field '_product_image_gallery' to be copied as it was previously configured incorrectly. To change the translation settings for this custom field, we: - Went to WPML -> Settings -> Custom fields translation - Clicked on 'Show system fields' - Searched for '_product_image_gallery' - Changed the configuration to copy.
If the 'Duplicate uploaded media to translations' option is not being applied to all products, further investigation may be required to set it in bulk.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related 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.
Problem: If you're experiencing an Internal Server Error while trying to customize your site in another language, it's important to identify the cause of the error. Solution: First, we recommend enabling the WordPress debug mode to gather more information about the error. To do this, edit your
directory that contains any errors. Please check this log file and share the contents with us so we can better understand what's causing the Server Error 500. You can find more information on debugging in WordPress in the official WordPress documentation. Additionally, if the issue is related to the .htaccess file being rewritten with language folders, please follow the workaround provided in the WPML errata page. Remember to back up your database before making any changes.
Please note that the solution provided might be outdated or not applicable to your case. If after trying the above steps the issue persists, we highly recommend checking the related 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, don't hesitate to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client's website has two languages, English as the primary language and Finnish as the second language. The issue is that when clicking on product categories in the header on the Finnish version of the site, the language switcher does not appear, and users cannot switch between languages.
Solution: First, we noticed that the link from the menu goes to a non-existing category page, which is why the language switcher was not appearing. The correct link should use the 'tuote-osasto' slug instead of 'category'.
We advised the client to: 1. Go to the Finnish menu and adjust the URLs manually. 2. If it's a regular WordPress menu, edit it from Appearance → Menus, and select the second language next to the pencil icon. For more details, see our documentation on translating menus.
Additionally, we ran WPML > Menu Sync, and it resolved the issue. We also suggested that the client manually adjust the Finnish category names to be shorter if they are too long and causing layout issues.
If this solution does not apply to your situation because it might be outdated or not relevant 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. If you need further assistance, please contact us in the WPML support forum.
Problem: The client was experiencing issues with pages disappearing when WPML was activated. After setting up a copy of the site, they encountered an error indicating that the WPML table 'wp_icl_strings' was missing.
Solution: 1. We suggested that the client ensure their site backup includes the WPML tables. If the tables are missing, they should follow the workaround to recreate the missing tables found here: Missing WPML tables documentation. 2. We recommended backing up the database before making any changes. 3. We asked if the original site from where they migrated had the same issue. 4. We advised the client to update their WPML plugin to the latest version and also update all add-ons. The latest versions can be found under "My Account -> Downloads" on the WPML site, and update instructions are available here: WPML update instructions. 5. We reminded the client to back up their database before proceeding with the update, suggesting the use of a plugin like Duplicator.
If the provided solution is not relevant due to being outdated or not applicable to your case, we highly recommend checking the related 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 with us.
Problem: Additional strings are in English instead of French, possibly due to the WP Cookie consent plugin having a language selector in its settings, while the site's main language is French. Solution: We recommend changing the source language of the strings to English and then translating them into French. You can follow the steps provided in our guide on how to change the source language of strings:
If this solution does not apply to your case, or if it seems outdated, we encourage you to 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 visit our support forum: WPML Support Forum.
Problem: The client did not have any translation credits despite purchasing the Multilingual CMS package.
Solution: We have assigned the missing 90,000 credits to the balance of the client's account. We recommend the client to check their account balance to confirm that the credits are now available.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we encourage you to open a new support ticket. We also highly recommend checking related 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 contact us through the WPML support forum.
Problem: The client is using WP Cookie Consent to display a cookie banner consent and has translated all the necessary strings into French. However, while the buttons on the banner appear in French, the text content remains in English. Solution: 1. Go to WPML-> Theme and plugins localization, select your theme/plugin, and scan. 2. Navigate to WPML-> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the needed strings. 5. Select the strings. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the strings, clear the cache, and check the front end.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 with us.
Problem: The client was experiencing an issue where translations in the joined segments were being deleted after editing the original content.
Solution: We explained that if the client translates sentences before joining them, the translations should remain intact in the Advanced Translation Editor when editing the original sentences. However, if the client joins sentences and then translates them into fewer sentences, the translation may be lost because the translation memory cannot recognize the translation of each individual sentence. For instance, if the client has three sentences and translates them before joining, the translation will not be lost upon editing the original sentences. But if the client translates three sentences into one, the translation will be lost. We recommended reading more about this issue in our documentation: https://wpml.org/faq/why-arent-my-translations-showing/#why-does-my-translation-disappear-from-the-advanced-translation-editor-when-i-update-my-default-content.
If this solution does not apply or is outdated, or if you are still experiencing issues, 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.
Problem: The client was unable to translate a template using the Betheme theme, as the template would load indefinitely without displaying the translation. Solution: 1. We asked the client to attempt the translation process again and inform us if the issue persisted. 2. We attempted to log in to the client's site to investigate the issue but encountered an error. 3. The client resolved the issue on their own after adjusting the GeoIP server settings, which had been blocking access.
If you're experiencing a similar issue with translating templates in Betheme or any other theme, we recommend you: - Ensure that there are no server settings, such as GeoIP restrictions, that may be interfering with the WPML plugin's operation. - Try the translation process again and check if the issue persists. - If the problem continues, please open a new support ticket with us.
Please note that the solution provided might be outdated or not applicable to your case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Problem: The client is experiencing a recurring issue where the default language page shows blank due to memory exhaustion errors, despite having 512MB of memory allocated. This problem was similar to an issue discussed in a previous support ticket.
Solution: We recommend checking with the hosting/service provider as the "allowed memory exhausted" error is typically related to server or hosting settings. It may be necessary to increase the memory limit beyond 512MB, as some sites require more resources, especially if the error occurs intermittently, suggesting that the server runs out of resources over time. For more details, see the discussion on a similar issue: https://wpml.org/forums/topic/allowed-memory-size-of-536870912-bytes-exhausted-tried-to-allocate-20480-bytes/#post-11770711.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 none of these steps resolve the issue, please open a new support ticket with us.
Problem: The client was unable to translate the header and footer using Elementor and encountered a 502 error when switching to the English version of the homepage.
Solution: 1. We asked the client to perform a full backup and provide us with WP admin access to investigate the issue. 2. We suggested the client disable any firewall that might be interfering and clear the server cache. 3. We used a VPN to access the site from a different location when we encountered access issues. 4. We requested FTP access to check the files directly but ended up using a file manager plugin instead. 5. We obtained permission to deactivate plugins to identify any conflicts. 6. After deactivating certain plugins, we were able to create a new page and the English version of the homepage started working, including the header and footer. 7. We reactivated the plugins one by one to pinpoint the cause of the issue. 8. We provided the client with direct links to the header and footer post types in the WP admin to facilitate the translation process:
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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 for further assistance.
Problem: The client is unable to translate WooCommerce emails using WPML and the Kadence Email Designer. They followed the WPML guide for translating WooCommerce emails but encountered an issue where WPML's String Translation returned 'NO strings found' when attempting to add translations. Solution: We advised the client to ensure that they have entered data into each field within the WooCommerce email templates, as placeholders are not available for translation. After filling in the email template fields, the client should: 1. Navigate to WPML > Theme and Plugin Localization and scan the WooCommerce plugin for strings. 2. Once the scan is complete, search for the email strings in the Admin screen and include those strings for translation. We provided documentation to assist with finding and translating strings that do not appear on the String Translation page: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/#translate-admin-and-settings-strings We also reminded the client to revisit the guide for translating WooCommerce emails: https://wpml.org/documentation/related-projects/woocommerce-multilingual/how-to-translate-woocommerce-emails/ If the provided solution is not relevant due to being outdated or not applicable to the client's case, we recommend opening a new support ticket. We also suggest checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed.
Problem: The client was unable to see all three languages (Croatian, English, and Italian) on their website using the APicona theme and was encountering issues with the language flags not displaying correctly. Additionally, there was an error message indicating a missing database table related to WPML. Solution: We suggested that the client should complete the WPML configuration wizard, as it appeared that WPML had not been fully set up on their site. This could have been due to a recent reset or migration. Completing the setup would involve adding all the necessary languages. We also advised checking for any known issues with the APicona theme and WPML compatibility.
If you're experiencing similar issues, we recommend you try completing the WPML configuration wizard to ensure all languages are properly set up on your site. If the problem persists, it might be due to an outdated solution or a different case. In such instances, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If these steps do not resolve your issue, please open a new support ticket with us.
Problem: The client wanted to change the background color of the active language flag in the mobile menu to make it distinct from the other languages.
Solution: We recommended adding custom CSS to achieve this. Here are the steps we provided: 1. Navigate to Appearance > Customizer > Custom CSS. 2. Insert the following CSS code:
@media screen and (max-width: 1024px) {<br />.elementor-element.elementor-element-345165c.elementor-hidden-desktop.e-con-full.e-flex.e-con.e-child .wpml-ls-current-language a {<br />background-color: #BB6D00 !important;<br />}<br />}
3. Save the changes.
This CSS snippet targets the active language flag within the mobile menu and applies a specific background color to it.
Please note that this solution might be outdated or not applicable to your case. If it doesn't help, we encourage you to open a new support ticket. We also highly recommend checking related 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 contact us in the WPML support forum.
Problem: 1. The client wants to know the cost of bulk automatic translation before proceeding. 2. The client wishes to set all automatic translations to a "review" state for human translators to verify. Solution: 1. To estimate the cost of bulk automatic translation, we recommend checking out these two resources:
Please note that the solution provided might be outdated or not applicable to your case. If so, we encourage you to 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. If you need further assistance, please visit our 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
