Problem: The client was unable to translate certain strings from the "User registration" plugin, specifically the "Take Picture/Upload File" and Calendar items. While the issue with "Take Picture/Upload Files" was resolved, the Calendar remained untranslated.
Solution: 1. We suggested checking the WPML > String Translation section and enabling the "Look for strings while pages are rendered" option. Then, visit the page where the string appears and return to the String Translation page to search for the string again.
2. If the string is not found in the String Translation, it might be registered as admin text. We provided a link to the documentation on how to find and translate admin text strings:
3. We acknowledged that the issue with the calendar might be due to the plugin not being fully compatible with WPML. We recommended contacting the plugin authors to inquire about WPML compatibility and, if necessary, inviting them to join our 'Go Global' program for assistance in making their product fully compatible with WPML.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket with us.
Problem: The client purchased the WPML plugin and found that it lacks the functionality to create a pop-up window for language selection, which is crucial for their project. The client has decided that WPML does not meet their specific needs and has requested a transaction cancellation and a refund. Solution: If you're experiencing a similar issue and have concluded that WPML does not meet your needs, we recommend that you apply for a refund directly through your WPML.org account. Please visit the following link to proceed with your refund request: https://wpml.org/purchase/refunds/. We, as the WPML support team, do not have access to the refund procedure, so this is the best way to initiate your transaction cancellation.
If this solution doesn't look relevant to your situation, please open a new support ticket at our support forum.
Problem: The client reported that a quiz feature on their staging site was working in Hebrew, English, Arabic, and Russian, but not in French and Spanish. They identified that special characters in translated strings were causing the issue and temporarily removed the translation.
Solution: We advised the client that supporting custom code falls outside our support scope, but we provided guidance to help resolve the issue. We recommended using gettext calls to make strings added with custom code translatable and provided documentation links:
$my_current_lang = apply_filters( 'wpml_current_language', NULL );<br /><br />if($my_current_lang=='fr'){<br />//Custom code for French quiz<br />}
If these solutions are not helpful, we recommended trying one of the WPML-compatible plugins listed here: WPML-compatible plugins. Alternatively, the client can seek assistance from a third-party contractor or developer, with a list of certified contractors available here: WPML-certified contractors.
If this solution doesn't look relevant, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue with duplicate pages for the same translated tag on their multilingual website. Solution: If you're encountering duplicate tag pages on your multilingual site, you can delete them with the following steps: 1. Ensure you have a full backup of your website. 2. Navigate to Posts > Tags. 3. Change the admin language to the language of the duplicate tags (Spanish in this case) using the language switcher in the top admin bar. 4. Select the duplicate tags and delete them.
Problem: The client has a bilingual website and has updated the text in WooCommerce completed order emails. The new text shows correctly in the WooCommerce dashboard under Settings - Emails, but clients receive the old version. In WPML String Translation, the old text still appears for the original language, while the new text is incorrectly displayed as the translation for the second language. Solution: 1. Navigate to WPML -> String Translation. 2. Select the email strings. 3. Delete them. 4. Go to WooCommerce -> Settings -> Emails tab. 5. Edit the email. 6. Click the save button. 7. Click Translations. 8. Translate the strings. 9. Verify if the issue is resolved.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is trying to translate an Elementor website with WPML and is facing two issues: 1. The translation editor does not show the word "Published" from the "Before" field in the Elementor post meta data element. 2. WPML creates a separate template for each language, which means design changes in the default language template must be manually replicated in each translated template.
Solution: 1. When making design/layout changes or adding new widgets to the default language template, update the translation using the Translation Editor, not Elementor. Follow these steps: - Create a test template - Add a heading and text widgets - Translate the template - Edit the template in the default language - Add a new widget or change the color of existing ones - Update the template and its translation via the translation editor - Check the translated template on the front end
2. To add the untranslated string "Published" to the translation editor, register the widget for translation by following these guides:
Problem: In a multilingual WooCommerce setup with Greek as the primary language and English as the secondary language, not all products are displayed when switching to the English version, despite being synchronized in each language. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML -> Support -> Troubleshooting. 2. Execute the functions listed one by one. For guidance, please refer to this documentation. 3. Clear your site's cache and then check the products on the front end.
⚠️ Please ensure you back up your database before performing the above steps.
If this solution doesn't look relevant to your issue, please open a new support ticket in our support forum.
Problem: The client is unable to find strings to translate in the footer area 4 widget on their website.
Solution: 1. Ensure a backup of the website is taken for safety reasons. 2. Update the WPML plugins to the latest version by following the steps provided in the WPML support forum thread. 3. After updating, translate the widget by: - Navigating to WPML >> String Translation page. - Clicking on the Translate texts in admin screens » link at the bottom. - Searching for the required string. - Selecting the string and clicking on the Add to String Translation button. - Returning to String Translation and adding the translation. For more details, refer to the documentation on translating texts in admin screens. 4. If the widget still does not show the correct translation, add the following Custom XML Configuration to WPML >> Settings > Custom XML Configuration section:
Problem: The client is attempting to translate the footer from English to Arabic using two Penci blocks, one for each language. They have tried to add the block to string translation via the 'Admin Texts Translation' but it was not successful. Solution: 1. We resolved the issue by translating the footer slug instead of the footer ID. We recommend checking the footer translation by visiting this link and ensuring it works correctly in both languages. 2. We advise keeping the strings in the Soledad > Theme option > Quick text translation in English, and then translating them to Arabic via WPML -> String Translation.
If this solution does not seem relevant to your issue, please feel free to open a new support ticket by visiting the WPML support forum.
Problem: The client wants to hide the language switchers on their WPML enabled site except for certain logged-in admin users. Solution: We recommend hiding the secondary languages, which will also hide the language switcher. You can do this by navigating to WPML -> Languages -> Hide languages section. For more information, please visit hiding languages on the front-end.
To allow hidden languages to be accessible to specific users, go to Users -> All Users, click 'Edit' next to the user you want to grant access to. In the WPML language settings section, check the Display hidden languages checkbox and then click the Update Profile button to save the changes.
If this solution does not seem relevant to your situation, please feel free to open a new support ticket in our support forum.
Problem:
Client's website main site is in Dutch, and the translation is in German. The backend shows the correct translation, but the website itself does not reflect the new translations, displaying old dates from 2021. Solution:
If you're experiencing an issue where the backend translation is correct, but the changes are not visible on the website, we recommend you try the following steps:
- Ensure you have a backup of your website.
- Navigate to WPML -> Support in your admin dashboard.
- Click the "troubleshooting" link below the plugin versions list.
- In the "Clean up" section, perform the following actions:
# Clear the cache in WPML
# Remove ghost entries from the translation tables
# Fix element_type collation
# Synchronize local job ids with ATE jobs
# Synchronize translators and translation managers with ATE
# Set language information
# Fix post type assignment for translations
- After completing the cleanup, go to the affected page and make a minor modification to the content in the original language.
- Attempt to translate the page again and check if the issue is resolved.
Remember to clear any existing cache on your website and in your browser after performing these steps.
Problem:
When using WP Job Manager, the categories are visible in all languages simultaneously, which is not the desired behavior. The categories should only appear in the language in which the job is posted.
Solution:
First, ensure that the taxonomy 'job_listing_category' is set to be translatable: 1. Navigate to WPML > Settings. 2. Scroll down to Taxonomies translation. 3. Change the translation preference of 'job_listing_category' from 'Not translatable' to 'Translatable'. After this change, you will need to translate the terms since they are currently registered under the primary language. To translate them: 1. Go to WPML > Taxonomy Translation. For more information, please refer to our documentation on Translating Post Categories and Custom Taxonomies.
If this solution doesn't look relevant to your issue, please open a new support ticket in our support forum.
Problem: The client is trying to translate pages but instead of seeing the translation page, they are redirected to the WordPress Panel Page. Solution: 1. We recommend ensuring that under WPML > Settings, the Advanced Translation Editor is selected. 2. Choose the option "Translate some". 3. When editing the default-language page, make sure that on the right sidebar, the option "Use WPML Editor" is not turned off.
Problem: The client was setting up WPML and encountered a red warning stating that WPML is missing some records in the languages tables, which could prevent it from working properly. The client attempted to resolve the issue by following the suggested fix to 'Clear language information and repopulate languages' on the Troubleshooting page, but it did not resolve the warning.
Solution: We discovered that the issue was related to the site's cache. By adding a URL parameter to the page where the warning was displaying, we were able to view the uncached version of the page, which did not display the notification (meaning the fix had been applied). Additionally.
If you're experiencing a similar issue, we recommend trying to view an uncached version of your site by adding a URL parameter to the address or flushing your server-side cache (not to be confused with a cache plugin). If the problem persists, please open a new support ticket with us.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
