Problem: After updating the Organic Builder Widgets Pro plugin, the translated French homepage is not displaying correctly, showing an error message. The widgets appear in English but not in French or Spanish when accessed through the WordPress customizer. Solution: 1. Edit the homepage in the original language. 2. Make a small change to the content, especially in the elements that are not correctly translated. 3. Save the changes. 4. Update the translation and double-check if the issue has resolved. If the problem persists, it might be due to the widgets not being correctly registered with WPML. Ask the developer if the widgets are registered in WPML and refer them to the documentation on achieving WPML compatibility for themes and plugins at https://wpml.org/documentation/support/achieving-wpml-compatibility-for-your-themes-and-plugins/ and the Go Global program at https://wpml.org/documentation/support/go-global-program/.
If these steps do not resolve your issue, or if the solution seems 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to translate WooCommerce Checkout Manager by quadlayers using WPML. Solution: If you're experiencing this issue, we recommend trying the following steps: 1. Navigate to WPML → String Translation. Scroll to the bottom of the page and click on the Translate texts in admin screens link. This will direct you to a searchable list of admin strings. Search for your specific string, select it, and then click Add to String Translation. 2. Alternatively, you can make a small change to the field title or content and save it. Then, go to WPML > String Translation > Translate texts in admin screen, search for the adjusted string, and add it to String Translation. Finally, translate the string using the WPML String Translation. For more detailed guidance, refer to our documentation on translating admin and settings strings.
Please note that this solution might be 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 an issue where you cannot edit a translation on your homepage and encounter an error message, follow these steps to troubleshoot. Solution: First, navigate to WPML → Support and click on the Troubleshooting link. On the WPML Troubleshooting page, click the button labeled Force-enable WPML’s Advanced Translation Editor. If this does not resolve the issue, try updating the page translation by making a minor modification to the original page (like adding an extra dot), then remove it and save the changes. This should prompt the system to indicate that the translation needs an update, allowing you to access the WPML translation editor successfully.
If the solution provided here becomes irrelevant due to updates or does not apply 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with duplicate activity entries in BuddyBoss when adding a new job in WP Jobmanager, and the links for each language in the activity entries are incorrect, this is a known issue. The problem arises because when a job post is created and set as translatable in WPML, translated posts are automatically generated in all languages, leading to multiple activity posts. Solution: Currently, there is no direct workaround from our side as this issue requires adjustments in the BuddyBoss plugin. We recommend monitoring the BuddyBoss updates and checking the related known issues on our site. You can view the specific issue here: https://wpml.org/errata/buddyboss-posts-and-activities-not-filtered-by-language-on-feed-pages/. Additionally, there is a client-suggested workaround that might help, but it could break pagination. You can find more details here: https://wpml.org/forums/topic/filter-by-language-does-not-work-for-activity-feed/page/2/#post-13969021.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Please also check related known issues (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 contact us directly at the WPML support forum.
The client no longer uses the SEOPRESS plugin but still sees the SEOPRESS area on the WPML translate page and wants to delete the translation area for inactive plugins.
Solution:
First, ensure you have a site backup. Then, follow these steps:
1) Navigate to WPML>>Settings>>Custom Fields Translation. 2) Click on the Show system fields link. 3) Search for
seopress
fields. 4) Set Don't translate as the translation option for all
seopress
fields. 5) Save the changes.
Afterwards, refresh the translation settings by:
1) Opening the Page for editing in the default language. 2) Making a minor change in the page contents and updating it. 3) Visiting WPML>>Translation Management Dashboard. 4) Choosing the Page you want to translate or updating the existing translations. 5) Sending it to Translation Basket. 6) Visiting WPML>>Translation Management>>Translation Basket. 7) Sending it for translation, choosing yourself as a translator. 8) Visiting WPML>>Translations queue and translating the page by clicking the Translate button.
For more details on the correct workflow for translation, refer to this article.
If this solution does not apply because it is outdated or not relevant to your case, 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. For further assistance, please visit our support forum.
Problem: You are trying to translate a page on your website and encounter an error message: 'Someone is already rating this translation. Please try again later.' even though you are the only one working on the website. Solution: If you're experiencing this issue, we recommend you try clearing your cache as this resolved the problem for the client. Please note that the 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 problem still exists, please open a new support ticket.
Problem: The client was unable to edit or add images to translated products using Advanced Custom Fields (ACF) with WPML. The images appeared on the translated product, but the edit/remove functions were not available, and the 'add image' button did not appear. Solution: The issue was not related to WPML but was caused by outdated PHP code in the template that defined the ACF field group and its settings. This outdated code interfered with newer versions of ACF, preventing several UI elements from loading properly. The client resolved the problem by removing this outdated PHP code, restoring functionality to the UI elements.
If you're experiencing similar issues, we recommend checking for any outdated code or settings in your templates that might affect ACF's functionality. Additionally, ensure that your theme and other plugins are not causing conflicts. You can do this by switching to a default WordPress theme like TwentyTwenty-Four and deactivating all plugins except for WPML and ACF. If the problem persists, activate the plugins one by one to identify the culprit.
Please remember to back up your site before making any changes. If your site is live, consider performing these checks in a staging environment.
If this solution does not apply to your case, or if it seems outdated, please visit our known issues page and confirm that you have installed the latest versions of themes and plugins. If the issue persists, we highly recommend opening a new support ticket with us here.
Problem: The client is experiencing 404 errors when trying to recreate trashed pages with identical names and permalinks on a site using WPML. The issue does not occur when WPML is deactivated, and it does not appear on a staging site. Solution: We identified that the problem might be related to caching mechanisms used by WPEngine plugins on the live site. Clearing the cache resolved the issue, allowing pages to be recreated without returning a 404 error. If you're experiencing this issue, we recommend trying to clear your site's cache. Additionally, ensure that any caching plugins or systems, particularly those related to object caching, are properly configured or temporarily disabled when making such changes.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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 necessary, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing a PHP Fatal Error when trying to save a translated page using WPML with the Avada theme. The error message indicates an 'Uncaught InvalidArgumentException: No translation entry found'.
Solution: We recommend the following steps to resolve the issue: 1. Navigate to
Avada > Library
in your dashboard. 2. Identify the Library Elements designated as Global. 3. Access the translations for these Global Library Elements and ensure they have been translated independently. For guidance on translating items independently, please refer to the following article: Translating Independently.
If the issue persists after following these steps, 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 WPML Support Forum.
Problem: You are trying to translate the email texts of the 'Five Star Restaurant Reservations - WordPress Booking Plugin' for your Italian website. Although you have translated the strings in the WPML string translation tool, the email notifications are still being sent using the German (DE) template instead of the Italian (IT) one. Solution: First, ensure that you have translated the specific strings related to the booking notifications. You can find these strings by searching for '[rtb-settings]template-booking-user' and '[rtb-settings]subject-booking-user' in the WPML string translation tool. Here is the link to directly access the string translation page: Translate strings. If translating these strings does not resolve the issue, it is possible that the strings are stored elsewhere in the database by the booking plugin. We recommend contacting the support team of the 'Five Star Restaurant Reservations - WordPress Booking Plugin' to inquire about the storage of these strings.
Please note that the solution provided might be outdated or not applicable to your specific case. If the issue persists, 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, do not hesitate to open a new support ticket with us for further assistance.
Problem: The client is trying to translate the WP Cookie Consent plugin using WPML but is unsure how to proceed. Solution: We recommend using the WPML String Translation to translate all strings of the WP Cookie Consent plugin. If some strings are missing, you should register them to appear in the translation table. You can do this by following the steps outlined in Finding Strings That Don’t Appear on the String Translation Page. It is advisable to use the "Admin Strings" option. Once activated, open the Frontend, and WPML will attempt to automatically register all visible strings.
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 experiencing issues with the ATE UI not maintaining the selected version preference (old UI), as it reverts to the new UI after some time or following updates.
Solution: We suspect the issue might be related to browser caching. When switching between the new and old UIs in ATE, a parameter in the URL (i.e.,
ui=gen3
for new and
ui=legacy
for old) dictates which UI version to display. This setting should persist unless manually changed. We recommend clearing your browser cache to ensure this setting is applied correctly. Additionally, keep your plugins and themes updated to benefit from the latest fixes and improvements.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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. If problems persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing an issue where WPML changes the order of product variants between languages, specifically from Croatian to Swedish, despite using compatible plugins like Hello, Elementor PRO, and Variation Swatches for WooCommerce. Solution: To ensure the variant order remains consistent across languages, follow these steps: 1. Navigate to your WordPress Dashboard and go to Products > Attribute. 2. Hover over the attribute in question and click the "Configure terms" link. 3. Change the language from the top admin bar to the language that has the incorrect order. 4. After the page loads, you will see that each item has a handlebar on the right of the row. You can drag and drop these handlebars to reorder the variants correctly.
If this solution does not resolve your issue, or if it 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where the language switcher does not work for a specific language, such as German, and navigating from the Dutch homepage to the German homepage results in a 404 'nothing found' error, while the direct URL (e.g., https://hpstaal.nl/de/home) loads fine, the problem might be related to your WordPress reading settings. Solution: We recommend checking your WordPress reading settings. Specifically, ensure that 'Your homepage displays' is set to show a static page instead of 'Your latest posts'. You can find this setting under WordPress Reading Settings. Set it to display the 'Home' page as the static page.
If this solution does not resolve your issue, or if it seems 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. Additionally, you can open a new support ticket for further assistance 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
