Problem: The client is trying to approve translations to display them on the frontend. The translation dashboard shows an "in progress" icon with a message "Spanish: Waiting for translator", but the translation queue is empty, displaying "no data". The client, operating as an Admin and assigned as a translator for English to Spanish, is unable to add themselves as a Translation Manager, and the search form for accounts is persistently blank. Solution: We discovered an issue with the WPML string tables, which is likely causing the problem with the translation editor. Although the usual workaround was applied to the theme's functions.php file, it did not resolve the issue. We recommend resetting WPML entirely and installing it from scratch, as there appear to be no translations started since its installation. If you have not yet begun populating the site with translations, this should not result in a loss of data. If this solution does not seem relevant to your situation, please open a new support ticket with us.
The client mentioned that the custom post types listing does not work in the second language.
Solution:
The problem was that the single post types were not translated in the first place, and the translation of the post type listing had manual text inside Elementor.
The recommended way is to translate the post-type items and use the translation editor to translate the listing page to show all the content correctly on the second language.
Problem: 1. The client's primary navigation was not translated on any page except the home page. 2. The "Read More" button was not displaying its translation despite WPML indicating it was translated.
Solution: 1. For the navigation translation issue, we recommend enabling the option 'Adjust IDs for multilingual functionality' found in WPML -> Languages -> Make themes work multilingual. 2. For the "Read More" button, ensure that the string is correctly defined in the default language. In this case, the string 'Weiterlesen »' was incorrectly set as an English string. We corrected it by setting it as a German string and updated its translation to 'Read More »', which resolved the issue.
Please verify if these solutions have resolved the issues on your site. If this solution doesn't look relevant, please open a new support ticket.
Problem: The client is experiencing issues with the logout functionality on a site using WPML, and the provided documentation link was not helpful as it only addressed login and registration pages.
Solution: We recommend the following steps to resolve the logout issue: 1. Navigate to WordPress Dashboard > WPML > Languages > Language URL Format. 2. Ensure the Different languages in directories checkbox is selected. 3. Click the Save button. 4. Proceed to WordPress Dashboard > Settings > Permalinks. 5. Click the Save button to flush the permalinks cache.
Problem: The client is unable to add a registration key to the WPML plugin. Despite downloading the plugin from the WPML site and attempting to regenerate the key, the client receives an error message stating that the account has expired.
Solution: If you're experiencing issues with adding your WPML registration key, we recommend the following steps: 1. Navigate to WP Dashboard Menu >> Updates. 2. Click the "Check again" link. 3. Go to Plugins >> Add New Plugin > Commercial tab and click on the “Refresh account status” button (if available). If the problem continues, please try these additional steps: 1. Log in to your WPML.org account and visit the Sites page: https://wpml.org/account/sites/ 2. Delete the existing site key. 3. Log in to your WordPress site and go to Dashboard >> Plugins >> Add new > Commercial tab and click the Unregister WPML from this site link (if available). 4. Click the Register WPML link. 5. Click the Get a key for this site link to generate a new key. 6. Copy the new key, paste it into the input box, and press the Register button. For more detailed instructions, please refer to our documentation: https://wpml.org/faq/install-wpml/#register
Problem: The client's custom user role, created with the 'Members' plugin, lost access to WPML settings and translation capabilities after a WPML update. The user role has all the necessary admin capabilities, but still encounters errors such as not having the rights to translate content, and the translation '+' buttons are greyed out.
Solution: We recommend the following steps to resolve the issue: 1. Edit the file /wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wp/classes/User.php 2. Locate the code on line 222 and replace:
3. Ensure that the "Manage Options" capability is granted to the custom user role.
If this solution does not apply to your situation because it might be outdated or not relevant 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 our support forum.
Problem: The client imported translations from an XLIFF zip directory to the wrong language, despite the XLIFF files containing the correct target-language information. Solution: If you're experiencing an issue where translations from an XLIFF zip directory were imported into the wrong language, even though the XLIFF files specify the correct target language, we recommend providing us with detailed information about the steps you took and the results you obtained. This will help us understand the issue better and assist you in resolving it.
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, we suggest opening a new support ticket. We also 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 further assistance is needed, please contact us in the WPML support forum.
Problem:
Client was unable to change the slug of a translated page to "the-lake-project"; it kept reverting to "the-lake-project-12". The client had already deleted old String translations but the issue persisted.
Solution:
Eventually, the client discovered that old translated pages using the desired slug were causing the issue, and after deleting them, the problem was resolved.
Before making these changes, it's important to back up your website and database.
If this solution doesn't seem relevant to your situation, please open a new support ticket with us and we'll be happy to assist you further.
Problem: The client was experiencing issues with some pages still opening in the Classic Translation Editor instead of the Advanced Translation Editor after switching back to the Advanced Translation Editor in the settings. Solution: 1. We accessed the WPML settings. 2. We changed the option under WPML --> Settings --> Editor for translations previously created using Classic Translation Editor from "Classic Translation Editor (recommended)" to "Advanced Translation Editor". 3. We advised the client to delete any translation jobs that were in progress with the Classic Translation Editor from WPML --> Translation Management --> Jobs. 4. We provided a video tutorial for further assistance: https://komododecks.com/recordings/Mx0Gt88nPAgGvmfj0QDO.
Problem:
After translating the page, the logo link added with Divi points to the default language.
Solution:
The logo link was added as a relative link (/link) which can't be translated. The issue was resolved by editing the translated page with Divi then adding the correct link to the logo.
Problem: The client is experiencing issues with WooCommerce product filters not showing up in a secondary language when products are set to "use translation if available or fallback to default language" and attributes are not translated. Solution: 1. We recommend checking our compatibility page to ensure there are no known incompatibilities with your current plugins. 2. Consult our documentation on setting up a multilingual WooCommerce store. 3. Adjust the setting for untranslated attributes in WPML → Settings to ensure they display correctly when using the fallback option. 4. If products or attributes are already translated, ensure that all remaining attributes or products are also translated.
If this solution does not seem relevant to your situation, please feel free to open a new support ticket with us.
Problem: The client has moved a development site from a subdomain to another domain, which is the live domain, and is unsure what to select in the WPML message received in the backend regarding sharing translation memory and automatic translation credits. Solution: 1. If the client plans to continue using the development website, they should select 'Yes' to share automatic translation credits and memory between the two websites. 2. If the development website will no longer be used, WPML will transfer all related translation memory and account details to the new live website. 3. To complete the process, the client should: - Go to WPML → Translation Management. - Click the Tools tab. - Expand the Connected Sites section. - Copy the migration code. - Paste it on the live website to connect them. For detailed instructions, please refer to the following documentation:
Problem:
The client is experiencing a 2-3 second delay in the admin panel due to a WPML query that checks for users with translation capabilities in a large user database.
Solution:
We recommend modifying the has_users_with_capability() function in the wp-content/plugins/wpml-translation-management/classes/user/class-wpml-translation-roles-records.php file. Comment out the existing function code and return \"true\" like this
public function has_users_with_capability() {\n// \$sql = \"\n// SELECT EXISTS(\n// SELECT user_id\n// FROM {\$this->wpdb->usermeta}\n// WHERE meta_key = '{\$this->wpdb->prefix}capabilities' AND meta_value LIKE %s\n// )\n// \";\n//\n// \$sql = \$this->wpdb->prepare( \$sql, '%' . \$this->get_capability() . '%' );\n\nreturn true;// return (bool) \$this->wpdb->get_var( \$sql );
Please ensure to test this change on a staging site before applying it to the live site. If this solution does not seem relevant to your issue, please open a new support ticket with us.
Problem: The client needed to ensure that their location pages were not published in Spanish and that visitors would only see the English version, even if they manually added
/es/
to the URL. Solution: We checked the location posts and confirmed that the language switcher does not appear, indicating that the posts are available only in English. If the client wants to prevent access to the Spanish version even when
/es/
is manually added to the URL, we advised setting the post type to
"Translatable - only show translated items"
and not translating the posts. This will ensure that any attempt to access a Spanish URL will redirect to the English version automatically.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
