Problem: If you're experiencing issues with the shop page during automatic translations, such as missing images or the page not appearing correctly in languages other than Italian, and products not being displayed separately, the problem might be related to server resources or synchronization settings. Solution: First, ensure that your website meets WPML's minimum requirements by increasing the PHP memory limit. You can do this by: 1. Accessing your server via FTP and opening the wp-config.php file in your WordPress root directory. 2. Inserting the following lines just before /* That's all, stop editing! Happy blogging. */:
Next, try the troubleshooting option in WooCommerce Multilingual: 1. Navigate to "WooCommerce > WooCommerce Multilingual > Status". 2. Click on the "Troubleshooting" link at the bottom right. 3. Before starting the synchronization, ensure you have a backup of your database. 4. Select the option "Sync products categories (display type, thumbnail)" and click "Start".
If the issue persists, we need to understand how you inserted the image in the original language.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at WPML's known issues page, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem still exists, please open a new support ticket with us.
Problem: The client is experiencing an issue where ACF link fields on their multilingual website are always redirecting to the English pages, despite the content being translated into other languages. Solution: We recommend the following steps: 1. Ensure that you are using the "Page link" field for internal links, as WPML can automatically translate these. 2. If you are using a "link" field for internal links, consider changing the multilingual setup to "Expert" mode and then adjust the translation preference for this field from "Copy" to "Translate".
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: The client is trying to display media assets identically across different languages for a custom post type built with ACF. While the text field translation works, the image field and gallery field containing media do not show on the translated pages.
Solution:
The client was using ACF to create those custom fields, changing the translation preference of those fields fixed the issue.
"I have solved it by setting the gallery and image field as copy instead of not translating."
If the solution provided here does not apply to your case, or if it seems outdated, 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 do not hesitate to open a new support ticket.
Problem: The client is experiencing a menu transition issue after updating to a new version of WPML Multilingual CMS. The site functionality related to menu transitions is not working as expected. The client has confirmed that version 4.6.7 of WPML Multilingual CMS is stable with their site. Solution: We asked the client to confirm if the issue is not present in version 4.6.7 but occurs in version 4.6.9, including the updated WPML add-ons. If the client is using a staging site, we recommended trying our beta plugin 4.6.10-b.1. We provided instructions on how to install beta versions of WPML, which can be found at How can I install beta versions of WPML?
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If this is the situation, 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 further assistance is needed, please contact us through the WPML support forum.
Problem: The client wants to import Italian product translations into their site, which already contains products in the main language, German. They have a CSV file with the Italian translations, including columns for SKU, name, short description, and description.
Solution: Here are the steps to follow:
Export your default language content using WP All Export.
Edit the exported CSV to add a column for the unique identifier.
Delete the original content from the site.
Import the default language CSV file with the unique identifier column as New items.
After importing the default language content, proceed with importing your secondary language file.
If you need to connect translations programmatically, you can use the
wpml_set_element_language_details
hook. However, we do not provide custom coding services. For examples and explanations, check out our documentation on wpml_set_element_language_details and related support forum discussions. If you require further assistance with custom coding, consider hiring a professional from our list of WPML contractors.
Please note that this solution might be outdated or not applicable to your case. If the provided solution does not resolve your issue, 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 help, please open a new support ticket in our support forum.
Problem: The client has a multilingual site in English and French and wants URLs to follow the format domain.ca/en/post or domain.ca/fr/post. They have set up different languages in directories and use a directory for the default language. However, after WordPress or plugin updates, lines such as RewriteBase /en/ and RewriteRule . /en/index.php [L] are being added to the .htaccess file, and the client is unsure if their WPML language settings are correct.
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 you still need assistance, please open a new support ticket with us.
Problem: The client was able to create taxonomy terms with the same slug across different languages. He wanted to make sure that this would not result in duplicate slugs and creates issues with WordPress. Solution: We have confirmed that it is possible to have the same slug in different languages with WPML. This functionality was implemented following feature requests from customers. For more information and historical context, you can refer to the following resources:
If this solution does not apply to your situation, or if it seems outdated, we 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 do not hesitate to open a new support ticket with us.
Problem: The client is experiencing an issue where the Translation Management page shows the task status as Completed, but the related page appears empty despite the title. When editing the translation, all blocks seem translated, but the changes are not visible on the published page. Solution: We recommend the following steps: 1. Open the original page in the WordPress Editor and make a minor modification to the page title. 2. Save the changes to trigger a translation update. 3. Click on the update icon in the Language meta section and complete the translation update.
It's important to note that if the default page includes numerous external links, translating these links is necessary to ensure they display correctly in the secondary language. For guidance on translating links from the Translation editor, please check this guide: How to translate URLs with the Advanced Translation Editor.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking related known issues at WPML 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 in our forum: WPML Support Forum.
Problem: The client was inquiring about different methods of translating layouts in Divi Builder using WPML, the possibility of using the Divi visual builder for layout translations, translating taxonomy slugs to keep the same slug across languages, and forcing the default language to include the language code in the URL.
Solution: 1) We recommend not mixing different translation methods for the same item. If you're using the WPML translation editor, directly editing the translation can lead to problems. More details can be found here: Using different translation editors for different pages.
2) It is expected behavior that the Divi visual builder cannot be triggered while translating layouts because the "edit with the Divi builder" button does not appear in this case.
3) To keep the same slug for translated taxonomy, you need to enable the slug option in the WPML settings. Please refer to this documentation: Translating taxonomy slugs with WPML.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking related known issues at WPML 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: The client has a custom ACF block called Header Block with multiple fields (title, subtitle, content, button label, etc.), but only the button label is showing, and the other fields are not. The client is following the WPML documentation for translating sites built with ACF but is facing an issue because the field names are not unique across blocks.
Solution: We recommend ensuring that all field names are unique. This is a known limitation with ACF and WPML, as WPML handles custom fields by name, which are stored in the meta tables. Therefore, translation preferences are set by field name, necessitating their uniqueness. Here are some resources to help understand the importance of unique field names:
If this solution is not applicable due to it being outdated or not relevant 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 you still need assistance, please open a new support ticket.
Problem: The client's development server URL was visible in Google search results through WPML support questions, and they requested to make the tickets private and remove the URLs.
Solution: We removed any references to the development site URLs from the specified tickets.
Problem:
The client uses the legacy Views editor to create a View to display taxonomy terms.
The texts from the View are translated via String Translation, but on the translated page the View query returns no results, unlike in the default language where all of the taxonomy terms are shown.
Solution:
The problem was that the output of the View is ordered by a taxonomy custom field, and in WPML settings that term field is set as Do not translate. That means that in the secondary language the terms have no values for that custom term field.
It is a quirk of WordPress that when ordering by some thing, and potential results that have no value for that thing will be excluded from the results.
The solution is to copy or translate the custom term fields.
Problem: The client is experiencing issues with translating an empty slide-in cart on a WordPress website using Astra's slide-in cart for WooCommerce. The site's primary language is Serbian, and the secondary language is English. Everything except the mini cart when it's empty is translated into English. Solution: We recommend the following steps: 1. Ensure that you do not share your site credentials publicly for security reasons. 2. Select the string that is not translating correctly, change its language, and then translate it to the correct language. For detailed instructions, please follow 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.
Problem: The client was experiencing issues with CSS not being the same across different language versions of their website using the Divi theme. They noticed that custom fields were set to not translate and were unsure what this meant for their site.
Solution: We advised the client that the issue might stem from how the page builder or theme stores the styling information. We recommended setting the relevant custom field that contains styling information (usually containing words like "style", "css", "layout", or "styling") to "copy". This would allow the styling to be carried over to the translated page. The client should then: 1. Make a small change in the default language page. 2. Save the page. 3. Go to the translated page and save it again to ensure the CSS is copied over. For more detailed instructions, we provided a link to our documentation on translating custom fields: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/
If the solution provided here is not relevant due to being outdated or not applicable to your case, 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 further assistance is needed, please contact us in the WPML support forum.
Problem:
Client cannot use the WPML Media Translation plugin as it indicates 'Setup required' without showing how to complete the setup, specifically for translating images on an FSE homepage. Solution:
If you're experiencing an issue where the WPML Media Translation plugin is installed but displays a 'Setup required' message without further instructions, we recommend the following steps:
1. Deactivate all plugins temporarily.
2. Navigate to the Media Translation interface. A message should appear with a button to complete the setup.
3. Click the button to complete the setup process.
4. Reactivate the plugins that were previously turned off.
After following these steps, you should be able to use the WPML Media plugin for your needs, such as translating images on an FSE homepage.
Please note that this solution might be irrelevant if it's 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 for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
