Problem: The client needs to change the fallback language to English for the /en part of their site, without altering the default language from Italian to English. Solution: We explained that the fallback feature in WPML is linked to the default language, and currently, there is no option available to set a fallback language to a secondary language. Additionally, implementing such a feature would require custom coding, which is beyond the scope of our support as per our support policy.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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 asked if translating a product using WPML creates two separate products to be operated in the store (one in Polish and one in English), or if there is one product operated in two languages. They noticed that after translating the store, there were separate products for each language, which they had to handle separately. Solution: We explained that when a product is translated using WPML, a new product is indeed created and linked to the original one. However, any updates made to the original product, such as price, quantity, stock, and other parameters, are synchronized with the translated product. This means that the client only needs to translate the product text. For more detailed information, we recommended visiting the following links:
If the client is referring to specific layout settings being different between languages, these settings are typically controlled by the theme. If the theme uses custom fields to store layout settings for a product, these settings should be set to "Copy" to ensure that the same values are carried over when the product is translated. For further assistance on translating custom fields, we recommended visiting: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/#2-decide-how-to-translate-custom-fields
Please note that the solution provided might be irrelevant due to being 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 for further assistance.
Problem: You need to translate the menu headings in the footer, the button in the form, and all pages related to the store. The site uses an additional Elementor plugin, and you are unable to see options to create another version for the Arabic language and link it with the English version. Additionally, the automatic translation is not functioning as expected. Solution: To translate the contact form button, please edit the form in the original language, then edit the translation in the Advanced Translation Editor. Search for the button text and translate it. For the footer created with an Elementor template, translate the template and check the translation footer content in the frontend again. Refer to the documentation here and here.
For translating the footer template and other templates, go to WPML > Settings > Post types translation, set the post type "jet-theme-core" preference to "Translatable - only show translated items" and enable the "Translate - automatically" option. Refer to the documentation here.
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 here, 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 here.
Problem: You are unable to see untranslated pages in your menu editor or have them considered by the menu sync, even though you have set the post translation setting for pages to be translatable. Solution: If you're experiencing this issue, we recommend trying the following steps: 1. Navigate to Appearance->Menus and delete the "translated" menu. This action should allow your menu to display pages in both languages. 2. If the above step does not resolve the issue, consider duplicating the pages temporarily. You can do this through WPML->Translation Management. Select the pages you wish to duplicate and use the batch duplication feature to duplicate them in bulk.
If this solution does not apply to your situation, 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 you need further assistance. You can do so at WPML support forum.
Problem: You are using the Advanced Translation Editor (ATE) in WPML to update translations, but the changes are not appearing on the front-end of your website. Solution: We recommend updating the page translation. First, make a slight modification to the original page and save it. Then, navigate to the WPML translation editor and complete the translation. Ensure you back up your database before making any changes.
If the issue persists after following these steps, it might be due to settings that are either 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 you still need help, please open a new support ticket at WPML support forum.
Problem: You are using the User Ranks widget from GamiPress on your site with Elementor Pro and have translated the strings in WPML's String Translation. However, the widget does not translate on the frontend in the secondary language. Solution: Elementor Widgets cannot be translated directly using WPML > String Translation. Instead, you need to use the WPML Translation Editor, which by default supports all widgets that come with Elementor and Elementor Pro. Custom Elementor Widgets require an XML configuration to be translatable with the WPML Translation Editor. This configuration should ideally be provided by the plugin author in a
wpml-config.xml
file in the plugin's root directory. You can find a guide on how to register page builder widgets for translation here. If the plugin author does not provide this configuration, you can create one yourself and store it under WPML > Settings > Custom XML Configuration. Additionally, we offer a program to assist theme and plugin authors in making their widgets compatible, which you can mention to the author: here. Alternatively, you can use the WordPress Editor as the translation method. Instructions for translating with the WordPress editor can be found here.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues here, 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 here.
Problem: The client is experiencing a 404 page error when trying to navigate the Arabic version of their website or any article. Solution: We recommend checking if the issue might be related to a cached version of the page. Please try accessing the site from a different browser or device to see if the problem persists. If the issue continues, it could be beneficial to clear the browser cache or use a private/incognito browsing mode to ensure you are viewing the most recent version of the site.
If these steps do not resolve the issue, and you are still experiencing problems, 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 for further assistance. You can do so at WPML support forum.
Problem: The client wants a different site logo for each language on their WordPress site using a child theme of Twenty Twenty-One. They have translated the string [theme_mods_acorn]custom_logo with the relevant image ID but are still seeing the same logo across different languages. Solution: We recommend using WPML's String Translation to manage different logos for each language. Here are two methods to achieve this: Method 1: Navigate to WPML > String Translation. At the bottom of the page, enable the checkbox 'Look for strings while pages are rendered'. Visit the front end of a page displaying the logo, then return to WPML > String Translation and search for the string to see if it appears. Method 2: If the string does not appear in WPML > String Translation, it might be categorized as admin text. Follow the guide on finding and translating admin text strings: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
If these steps do not resolve your issue, or if the solution 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 needed, please open a new support ticket for further assistance.
Problem: The client is not receiving notifications and experiences delays in displaying translation changes, despite clearing WordPress cache, browser cache, and deactivating hosting CDN. Solution: We recommend checking the notification settings in the top bar of the ticket conversation.
Problem: The client reported issues with automatic translations being stuck and ACF fields not displaying correctly in the backend after migrating their site to a different WPEngine account. Solution: We edited and completed the translation jobs for the client. We asked the client to verify if the translations were now appearing correctly on the front end and if the ACF fields were visible in the backend. After reinstalling the plugins, the client confirmed that the issues seemed to be resolved.
If this solution does not apply to your case, 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 issues persist, please open a new support ticket.
Problem: The client wanted to use WPML with MateCat as described here: https://wpml.org/translation-service/matecat/. However, MateCat does not provide an API key. Solution: We recommend contacting MateCat directly to request the API key, as it's necessary for integration with WPML. If this is not possible, consider exploring other translation partners that we offer, which can be found here: https://wpml.org/translation-service/.
If this solution does not apply to your situation, or if it seems outdated, 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. For further assistance, you can visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing 404 errors on a multilingual website using the Milenia theme and MotoPress Hotel Booking plugin after translating the 'accommodations' slug. The URL slug alternated between 'nastaniavane' and 'accommodations' in the Bulgarian version, causing inconsistent behavior. Solution: The client resolved the issue by adjusting the slug translation settings in WPML. Instead of translating 'accommodations' directly to 'nastaniavane' in the string translation, the client set it to 'accommodations' in both English and Bulgarian. This change was then correctly reflected in the WPML settings for taxonomies and slugs, allowing the correct Bulgarian translation 'nastaniavane' to be used without causing errors. Additionally, we recommended troubleshooting steps such as clearing caches and synchronizing taxonomies in WPML if the problem persists. For detailed guidance on using WPML with MotoPress Hotel Booking, visit the following links:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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.
Problem: The client was unable to display one image on a translated page, despite having translated all content, including images. The issue was suspected to be related to incorrect settings in the PHP file for image translation preferences. Solution: We recommended checking the translation settings for custom fields, specifically ensuring that images are set to COPY rather than 'Copy-once' or 'Translate'. For detailed guidance on setting the correct translation preferences for field types, we advised visiting the following documentation: Recommended Custom Fields Translation Preferences for ACF and WPML.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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. For further assistance, you can contact us directly at the WPML support forum.
Problem: You are trying to add the Portuguese language with a 'pt' slug and encountering a notice in the admin dashboard stating that WordPress cannot automatically download translations for the Portuguese language with the current locale 'pt'. Additionally, when attempting to follow the suggested fix, you encounter an error stating 'The default locale already exists'. Solution: To resolve these issues, we recommend the following steps: 1. Activate the predefined Portuguese language with the language code 'pt-pt'. 2. Click on 'Edit Languages'. 3. Change the default locale for Portuguese to any value and then save. 4. Click on 'Edit Languages' again and set the default locale to 'pt_PT' for your new language. For more detailed instructions, please visit our documentation: Editing WPML's Languages Table.
If this solution does not apply to your situation, 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.
Problem: The client is preparing a website with only one language installed/active and is encountering notices related to the need for configuring additional languages to access 'Theme and plugins localization' and 'Media translation'. Additionally, editors receive a notice about using the Category translation table when accessing post categories, which they do not have permission to access. Solution: We recommend activating an additional language but keeping it hidden to avoid these notices. WPML allows the hiding of languages on the front end, which can help in preventing these messages without fully implementing a multilingual setup. For detailed steps on how to hide languages, please visit https://wpml.org/documentation/getting-started-guide/language-setup/hiding-languages-on-the-front-end/.
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 or 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