Problem: You need to translate scripts within a post, such as iframes or shortcodes, for different languages. However, when using the Advanced Translation Editor (ATE), you encounter issues where the original language script appears blank and modifications in the new language do not save correctly. After editing and saving the post, scripts revert back to the original language. Solution: We recommend not using the ATE for pages that contain scripts you need to translate. Instead, use a different method to manage translations for these specific pages to avoid the issues you're experiencing. For detailed guidance on how to implement this, please refer to our documentation on using different translation editors for different pages: Using Different Translation Editors for Different Pages.
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: If you're experiencing an issue where your shop page does not display the translated footer when switching languages, despite using Elementor and Elementor Pro for footer creation and translation, this summary might help. Solution: 1. Ensure the footer ID used in the Theme settings is correctly set for translation. Go to WPML > Settings and scroll to the bottom. 2. Click on 'Translate texts in admin screens »' and search for the default footer ID, which is
2092
. 3. If the ID appears, select it and click on 'Add to String translation'. 4. In the String Translation section, find the newly added ID and click on the '+' icon under the language flag. Enter the translated footer ID,
17945
, as the translation and save. Following these steps should ensure that the correct translated footer appears when switching to another language.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 https://wpml.org/forums/forum/english-support/.
Problem: You are working on a site using Elementor and WPML and want to know if changes made to the design in the main language will automatically be copied to the translated pages. You've noticed that the translated pages remain in the old design. Solution: When you change the design in the default language, you need to manually update the translation using the WPML translation editor to ensure that the new design is copied to the translated pages.
Please note that this solution might be irrelevant if it's 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: If you're experiencing issues where translated products are moved to draft status after importing them with All Import, while the main product remains published, this might be due to the settings in WPML. Specifically, this occurs when the 'Translated documents options' in WPML Settings is set to 'Publish the translated post when original is also published (default)'. This setting causes translations to mirror the status of the original post.
Solution: 1. Ensure that you import the default language of your site first. Automatic translation in WPML only functions from the site's default language to other languages. 2. If you need to handle multiple languages, consider using the WPML All Import plugin for importing and managing translations effectively. You can find the guide here: Import in one language & translate with WPML 3. For a more updated solution, use the WPML Export and Import plugin. Detailed guidance is available here: WPML Export and Import 4. Check if the necessary bridge plugins are installed on your site as they are essential for the imports to work correctly.
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 is unable to see credits in the WordPress dashboard after assigning them from their WPML account. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Log in to your WPML account and navigate to the Sites page. 2. Delete the existing site key. 3. Create a new subscription key for your site. 4. Go to your Site Dashboard, navigate to Plugins >> Add New >> Commercial tab. 5. Click on the “Unregister WPML from this site” button. 6. Register with the new site key and refresh the page.
This solution might be irrelevant if it’s 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 issue persists, please open a new support ticket.
Problem: The client wants to move the language flags from the footer to the header. Solution: 1) We recommend going to WPML-> Languages to configure the language switcher. For detailed guidance, please visit this guide. 2) To move the language switcher, you can either disable the footer and add a menu language switcher or use a shortcode to place the switcher in a new location. For instructions on using shortcodes, please check this guide.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are developing a site and using the WPML plugin, but you are asked to register the WPML plugin for updates even though your account is still valid. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Ensure that you are logged into wpml.org. 2. Navigate to
WordPress Dashboard > Plugins > Add New > Commercial (Tab)
. 3. Click the "Unregister" link. 4. Click the "Register WPML" at the right section of the screen. 5. Click the "Get a key for this site" link. A new page will open up, and the auto-generated key will appear in a pop-up. 6. Copy the key and paste it into the "Site Key" input box. 7. Click the "OK" button. For more information, please visit https://wpml.org/faq/install-wpml/#register.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum.
Problem: When translating products in WooCommerce, the YouTube video link included as the first additional image is not being copied automatically to other languages. The client needs to manually add the video link for each language translation. Solution: To ensure the video link is copied automatically when translating products, follow these steps: 1) Go to WPML>>Settings>>Custom Fields. 2) Click on the Show System Fields link. 3) In the search box, type URL to find the specific field. 4) Set the field to Copy and save the changes. 5) Open the product for editing in the default language and make a minor change to refresh the translation settings. 6) Update the product translation. For more detailed guidance, refer to our documentation on custom field translation preferences and translating custom fields.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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: The custom settings added by the Price Offers for WooCommerce Pro plugin are not being copied to the translated product data. Solution: If you're experiencing this issue, we recommend you navigate to WPML > Settings > Custom Field Translations and check for the fields related to the plugin. Set those fields to "Copy". This should ensure that when translating your products, the fields are copied appropriately. For more detailed guidance, please refer to our documentation on Translating Custom Fields.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with managing user-related functionalities such as username or email, reset password, login, and return to shop on their site. Additionally, a translated string is not showing up. Solution: If you're facing similar issues with translated strings not appearing, we recommend enabling the auto-register feature to find other instances of the string that might not be showing up. You can learn how to enable this feature by following the steps outlined in our documentation: Enable Auto-Register Strings.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your 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 through our support forum.
Problem: The client was experiencing 404 errors on newly published translated pages and products with incorrect or inconsistent permalinks. Solution: We recommended checking if the permalinks 'slugs' were correctly translated using the String Translation. It was suggested to reset these URLs to their default settings and then properly translate them. Additionally, we advised deactivating all plugins except WPML and switching to a default WordPress theme to identify any conflicts causing the issue. If the problem persisted, the next step was to create a staging site to further diagnose and resolve the issue without affecting the live site. After these steps, if issues with permalinks still occurred, it was necessary to ensure that slugs for different post types and categories were unique to avoid conflicts.
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. 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 setting up a multilingual site using WPML and encountered an issue where buttons on the German version of the site link to English pages instead of German ones. Additionally, the client needs to embed different shopping carts for each language. Solution: 1. We advised the client to check if the links in the buttons are using a relative path or a full path. If using a full path, changing it to a relative path might help. 2. We suggested using the WPML->Settings->Translate Link Targets and clicking on 'Scan now' to see if the links get adjusted. 3. If the issue persists, we recommended editing the page in the main language, making a minor modification (like adding an empty space), and then updating the translation. 4. As a test, the client was advised to edit one of the links in the main language to a relative path and then update the translation to see if the button points to the correct URL in the secondary language. 5. The client successfully resolved the issue by changing the links in the buttons to the short version and saving the translation again.
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 the problem persists, please open a new support ticket.
Problem: The client is encountering a fatal PHP error related to the WPML plugin, specifically an 'Uncaught Error: Call to a member function get_requested_lang() on null'. This issue typically arises from a compatibility conflict with another plugin or missing files in the WPML plugin. Solution: We recommend performing a full site backup before proceeding with any changes. After ensuring your site is backed up, please check the following tickets for potential solutions and workarounds:
If these solutions do not resolve the issue or if they seem outdated, 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 the problem persists, please do not hesitate to open a new support ticket with us for further assistance.
Problem: The client is unable to translate the Dutch text 'Wij helpen u graag!' on a specific page using WPML. All other items on the form are translated except for this one. Solution: We recommend checking which Avada Element is being used to display the text. This element may be missing the necessary WPML language configuration. For more details on how to register page builder content for translation, please refer to our documentation here: https://wpml.org/documentation/support/language-configuration-files/register-page-builder-content-for-translation/
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 https://wpml.org/forums/forum/english-support/.
Problem: You are experiencing issues with translating content created using the Revolution Slider and various widgets (e.g., Section Slider) on your WordPress site using the WPML plugin. Despite following standard procedures, you are unable to locate and translate certain strings from the Revolution Slider and widgets in the WPML String Translation section. Solution: We recommend following these guides to resolve your issue:
These guides provide detailed steps to find and translate the missing strings in the Revolution Slider and widgets.
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 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 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
