Problem: You are using WPML's String Translation to translate a field in the Theme options found in Customizer. While other fields translate correctly and show on the front-end, one specific field does not appear after translation. Solution: First, ensure that your theme supports the translation of this specific field. If the issue persists, follow these steps: 1. When adding a string from the admin text, select to export XML configuration. 2. Add the exported XML to WPML > Settings > Custom XML Configuration. This method helps WPML to manually detect and register the strings for translation, ensuring they display correctly on the front-end.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client had an issue where the field labels on an admin page created with ACF and displayed using
acf_form()
were not showing the translated versions after migrating the website, despite working correctly on the development site. Solution: First, we suggested checking if the translations for the labels were available on the migrated site by following this guide: Translating ACF field labels with WPML. If the translations were available but not appearing, we recommended regenerating the MO files: 1. Navigate to "WPML > Support > Troubleshooting". 2. Scroll down and click on "Show custom MO Files Pre-generation dialog box". 3. After the page refreshes, a popup will appear. Click on the "Generate MO File" button and wait for the process to complete.
If the solution provided here is not relevant due to being outdated or not applicable to your case, 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. Should you still need assistance, please do not hesitate to open a new support ticket. WPML support forum
Problem:
I'm using a custom code, I want to display the translation posts in the second language and fallback posts in the original language if the translations are missing with a custom query and Ajax. Solution:
Add the code below before the WP_Query in the Ajax callback function to show the fallback posts:
if ( class_exists( 'WPML_Display_As_Translated_Tax_Query' ) ) {
global $sitepress, $wpml_term_translations;
$wpml_display_as_translated_tax = new WPML_Display_As_Translated_Tax_Query( $sitepress, $wpml_term_translations );
$wpml_display_as_translated_tax->add_hooks();
}
Problem: The client wants to restrict authors to only see and edit their own posts of a custom post type in the admin area, as well as translate them, but currently, authors can access all posts. Solution: We recommend integrating with the Toolset Access plugin to manage user roles and permissions. This plugin allows you to restrict users to only see and edit their own posts of a custom post type. For step-by-step guidance, please refer to our documentation:
Problem: The client was trying to display a translated image field (a taxonomy field) with the Return Format set as "Image URL". While it worked in the original language, the translation returned the image ID as a string instead of the image URL. Solution: We checked the issue and found that the order in the English term did not match the default language term. We corrected this discrepancy. We then asked the client to verify if the English post now displays the image URL as expected. If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us.
