Problem: The client is trying to access the translation of menu items and is inquiring about the support for this feature as of July 2023. Solution: We are currently exploring ways to implement the translation of menu items. Unfortunately, we do not have an estimated timeline for when this feature will be available.
If this solution is not relevant to your case, because it might be outdated or not applicable, we recommend that you 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 you need further assistance, please visit our support forum.
Problem: The client is trying to translate the words "Next" and "Previous" using WPML String Translation but is having difficulty finding the correct strings due to multiple occurrences. Solution: We recommend searching for the strings within the WPML String Translation interface and filtering by the theme domain. This will narrow down the results and help identify the correct strings to translate. For detailed guidance on how to find and translate strings, please refer to our documentation on String Translation.
If this solution does not apply to your case because it might be outdated or not relevant, we suggest opening a new support ticket. We also 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 further assistance is needed, please contact us in the WPML support forum.
Problem: The client was experiencing a conflict when enabling WPML String Translation and Elementor Pro simultaneously, leading to a 500 error on their website. Solution: We recommended the following steps: 1. Verify that the server meets all WPML minimum requirements. 2. Consult our FAQ on 500 errors for potential solutions. 3. Enable WordPress debug to identify the specific error by following our debugging guide. 4. Perform a compatibility check by: - Creating a full website backup. - Disabling all plugins except for WPML and its add-ons. - Switching to a default WordPress theme like TwentySeventeen. - Reactivating plugins one by one to identify the conflicting plugin. 5. If the issue persists, it may be related to server/hosting settings, particularly the 'allowed memory size exhausted' error. We provided a custom search URL to explore existing tickets with similar issues and solutions. 6. We also suggested updating to the WPML 4.6.10 beta version after creating a full website backup and removing the current WPML version.
If these steps do not resolve the issue or if the solution is outdated or not applicable, we recommend opening a new support ticket. We also advise checking 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 needed to delete a website from their WPML account but was unable to find the delete button. They were able to remove the site from the 'Your Registered Sites' section but not from the 'Sites Using Prepaid Credits' section. Solution: 1. We asked the client to check if they had tried removing the site from the WPML account sites page at https://wpml.org/account/sites. 2. We inquired if the client could see a trash icon next to the domains on the same page, as shown in our provided screenshot. 3. We requested confirmation from the client to ensure the site no longer appeared in their account.
If you're experiencing a similar issue and the provided steps do not help, or if this solution doesn't seem relevant to your problem, please open a new support ticket at WPML support forum.
Problem: The client is running a multisite network and wants to show translations for zh-hans on the main site (finalto.com/zh-hans/) as well as on a subsite (finalto.com/sg/). Solution: We explained that WPML can be used on multisite setups, but each subsite will have a separate WPML installation and configuration. Translations cannot be connected between subsites. To display Chinese translations on another subsite, the client needs to export them from one subsite and import them into the other. However, it's important to note that the content will not be connected and each subsite will handle its content with its own WPML. We recommended checking our documentation on multisite support: https://wpml.org/documentation/support/multisite-support/ Additionally, we suggested using the following plugin for exporting and importing translations: https://wpml.org/documentation/related-projects/wpml-export-and-import/
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If this is the 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: https://wpml.org/forums/forum/english-support/
Problem: The client is trying to translate a media item and its URL in the header template.
Solution: 1. We recommend locating the source URL of the image in the WordPress media library by changing the language in the top admin bar. 2. In the Advanced Translation Editor, use the text field at the top left and type
http
to display all URLs used on the page for links and media. 3. Find the URL of your media file and replace it with the URL of the alternative media file from the media library.
For detailed instructions, please refer to our documentation on the Advanced Translation Editor:
Problem: The client was experiencing issues with the layout of the home page when switching to the French language, and sometimes pages would disappear after modifications. The problem seemed to be primarily with the navigation menu. Solution: 1) We permanently deleted the menu items that were in the trash and re-translated the pages. Then, we deleted the French menu and synced the menu again, which resolved the menu issue. 2) For the home page layout issue, we suggested that the client re-create the affected section in the default language and then update the translation to see if the issue persists.
If you're experiencing similar issues, we recommend you try the following steps: - Permanently delete any menu items in the trash and re-translate your pages. - Delete the problematic menu and sync it again. - Re-create any sections of your home page that are not displaying correctly in the default language, and then update the translation.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If these steps do not resolve your issue, 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 was experiencing an issue with the WPML language switcher being inconsistent with the themes installed. Solution: We found that the problem was related to the "Use menu cache" option in the ThemeREX Addons Settings. We recommended unchecking this option to resolve the issue. If you're experiencing a similar problem, navigate to your ThemeREX Addons Settings and uncheck the "Use menu cache" option.
Problem: If you're experiencing issues where your translated pages using Gutenberg FSE do not match the original English version, with only the header and footer displaying correctly, this might be due to your theme not being fully compatible with WPML.
Solution: We recommend deactivating your current theme and switching to a default theme to test if the translations work correctly. If they do, it suggests that the issue lies with your current theme's compatibility with WPML. Themes must adhere to certain conventions to be translatable with WPML. We have extensive documentation on how to ensure themes are translatable. Please contact your theme developer to verify if your theme is designed to be compatible with WPML and can be properly translated.
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, 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: After activating and configuring WPML on the client's website, all pages were redirecting to a 404 error page. Solution: We recommend taking the following steps to resolve the issue: 1. Ensure you have a full backup of your website and database. 2. Increase the 'WP Memory Limit' to at least 128MB, preferably 256MB. You can do this by adding the following code to your wp-config.php file:
Make sure to add these lines before the 'That's all, stop editing! Happy publishing.' line. 3. Deactivate all plugins except for WPML and its addons to check if the issue persists. 4. Reactivate each plugin one by one, checking your website after each activation to identify any plugin that may be causing a conflict. 5. If the problem continues, repeat the steps using a default WordPress theme, such as Twenty Twenty-One or Twenty Twenty-Three.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem 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 re-installed WPML on their blog and set Dutch as the default language and English as the secondary language. They wanted a language dropdown in the menu and footer. However, the website only displayed in English, and no language selector was shown. The client's attempts to remove the "/en" from the URL were unsuccessful, and the only solution seemed to be deactivating the WPML plugin. The issue persisted even though the client had set the website not to follow the browser's language settings. Solution: First, we asked the client to enable the WordPress debug log to identify any potential errors. We provided instructions and the necessary code to add to the wp-config.php file:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
We also requested that the client increase the WP Memory Limit to 256 MB and the MaxInputVars to 10000 for better performance, providing links to relevant documentation:
Upon further investigation, we found that the homepage had not been translated into Dutch. We advised the client to complete the translation of the homepage and check if the language switcher appears and works correctly on other pages, providing examples where the language switcher was functioning properly.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client reported that translations for a page that was previously 100% translated in French and English have disappeared from the backend, although they still appear correctly on the frontend. This issue occurred after making minor adjustments to the page.
Solution: We suggested that the problem might be related to the page builder used for the translations. We asked the client to confirm if the issue is occurring with text from Avada Builder or another page builder. Additionally, we recommended switching to the Advanced Translation Editor, which could help resolve the issue. We provided documentation on how to switch from the Classic Translation Editor to the Advanced Translation Editor:
If this solution 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: The client was experiencing an issue where the front page was correctly translated into English, but after adding new content (Pink Ribbon section), it only displayed in Dutch when English was selected. The client suspected that the recently installed LiteSpeed Cache plugin might be causing the translations to not show up correctly due to caching. Solution: 1. We checked the client's website and confirmed that everything was working correctly from our end. 2. We informed the client that the LiteSpeed Cache plugin is a popular caching solution that usually does not require special configuration with WPML and should not interfere with translations.
If you're experiencing a similar issue with translations not appearing correctly after installing a cache plugin, we recommend you: - Temporarily disable the cache plugin to see if that resolves the issue. - Ensure that the cache plugin is configured correctly to work with WPML. If this solution doesn't seem relevant to your situation, please open a new support ticket with us.
Problem: The client is experiencing an issue where the purchase confirmation email shows a duplicate string. Solution: We have released an update to address this issue. We recommend updating the WCML plugin to the latest version to fix the problem. If this solution doesn't resolve the issue or seems irrelevant to your situation, please open a new support ticket with us.
Problem: The client is unsure how to publish a post after adding a translation using the automatic translation feature with the setting 'Let me review it before it gets published' enabled. The translated post does not appear in the Translations menu, and the client is questioning whether the only way to publish is through the classic editor and how updates to the original post affect the translation.
Solution: First, ensure that automatic translation is activated by following our documentation: Automatic Translation Setup. If you're using the 'Translate What You Choose' option in WPML > Settings > Translation Mode, note that the 'Let me review it before it gets published' setting will not apply. By default, translated posts are published automatically once the original post is published. This can be configured in WPML > Settings > Translated documents options. If you have selected 'Save the translated post as a draft', then you must manually publish the post. To publish a draft, switch to the secondary language and click on the 'publish' button in the backend editor of the translated page.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive