Problem: The client experienced issues with the translation of filter labels in a bilingual website (Spanish to English). The labels were not saving correctly, and the translated values were not appearing on the site. Solution: We recommended manually adjusting the translated filter labels. However, upon further investigation, it was discovered that the JetFilters custom field translation settings had been modified incorrectly, setting many fields to "Copy". We compared these settings with a default installation and adjusted them on a staging site. We advised the client to apply the same settings from the test site to their production site by navigating to WPML → Settings → Custom Fields Translation and selecting 'Show systems fields'.
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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client followed the documentation to make user meta fields translatable and added the user type 'Vendor'. However, they encountered issues with finding the domain as shown in the documentation, and also faced problems with partial translations and automation of the translation process. Solution: We advised the client to configure the 'Vendor Plus' role to be translatable via WPML → String Translation. To ensure that the translated values display correctly on the front end, we recommended adding the following code snippet:
This filter enables WPML to return the translated value when user meta is retrieved. For automatic translations, although the 'Translate Everything' option does not include String Translation content, strings can still be translated automatically using WPML's automatic translation engine. However, they need to be sent for translation from the Translation Dashboard. For further details, please refer to our documentation: https://wpml.org/documentation/getting-started-guide/string-translation/
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client reported an issue where the 'Highlights' section appeared correctly in the backend of the translated property but not on the front end. The translated template was not fetching the correct taxonomy, and there was confusion about handling settings for dynamic fields and images in the translated template. Solution: We reviewed the translated template and corrected the source selection for the taxonomy. This resolved the display issue on the front end. However, the custom fields related to the 'Listing Source' and 'Query' values were not automatically copying from the default language due to their absence in the WPML → Settings → Custom Fields Translation. We suggested contacting the plugin author to inquire about setting these fields to Copy for WPML compatibility or to include the necessary WPML configuration in a future plugin update. If further assistance is needed, we recommend opening a new support ticket. Additionally, it's advisable to 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 this solution does not resolve your issue or seems irrelevant, please do not hesitate to contact us for further assistance by opening a new ticket at WPML support forum.
Problem: When translating a page, no content appears translated, and the translation editor shows zero words. Solution: The issue was traced to custom code in the child theme that was preventing WPML scripts from loading correctly. We recommend switching to the parent theme to verify if the translation editor then functions properly and the content becomes visible for translation. If the issue resolves, review and possibly disable parts of the custom code in the child theme to isolate the exact cause. If further assistance is needed, we suggest visiting our support forum.
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 problem persists, please open a new support ticket.
Problem:
Some pages fail to translate automatically, showing an 'Unable to retrieve job details' error despite standard troubleshooting attempts.
Solution:
The issue was caused by custom code added to the Astra Child theme used on the site. This code overrides part of our product’s core logic, preventing it from functioning as intended. As a result, switching to an alternative theme (or removing the conflicting customizations) was necessary to ensure full compatibility and proper operation of our product.
Problem: You are trying to update WPML but receive an error message stating that your site doesn't meet WPML's minimum requirements, even though the WordPress REST API is reachable. Solution: If you're experiencing this issue, we recommend trying the following steps: 1. Visit the following WPML errata page for a workaround: https://wpml.org/errata/warning-about-wordpress-rest-api-if-non-authenticated-requests-blocked/ 3. A permanent fix for this issue will be included in future WPML releases. Before making any changes, please ensure to back up your database.
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 problem persists, please open a new support ticket at WPML support forum.
Problem: You are trying to display a filter on translated pages using WPML, but the filter does not appear on these pages. It seems that the filter is present but attempts to pull content from the original language, resulting in it appearing empty. Solution: We recommend checking the configuration of your filter to ensure it is set to retrieve content based on the current language of the page rather than defaulting to the original language. This adjustment should allow the filter to display the correct content on translated pages. If this solution does not resolve your issue or seems outdated, please visit our known issues page and verify that you have the latest versions of themes and plugins installed. If the problem persists, we encourage you to open a new support ticket for further assistance. You can do so at our support forum.
Problem: You are trying to configure WPML to copy custom post titles instead of translating them, but some of your custom post types are translating titles when they should be copied. Solution: We do not have a built-in feature in WPML to exclude custom post titles from translation. This requires custom development. You can use the following example as a starting point: https://wpml.org/forums/topic/do-not-translate-title-with-automatic-translation/#post-13051837 Make sure to replace "product" in the code with your specific custom post type. Here is how you can modify the code:
$posttype == "your_custom_post_type"
Please ensure to backup your database before making any changes.
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 you still need assistance, please open a new support ticket at WPML support forum.
