Problem: The client is experiencing issues with translating certain strings on their website using WPML. Specifically, the button label 'Find Events', the placeholder 'Search for events', and dropdown options 'List, Month, Day' are not translating correctly. Additionally, custom text indicating the next lesson access date is not translating on the Spanish page, though it is available and translated in the backend. Solution: We recommend updating your WPML plugins to the latest version to ensure all translations are applied correctly. You can download the latest versions of WPML from here.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. We also 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, you can contact us directly through our support forum.
Problem: The client needs to make the heading text in a custom plugin translatable, as well as another text passed through using AJAX. Solution: For the heading text: 1. Ensure you use the
esc_html__()
function with the text domain specified, like this:
echo esc_html__( 'Text to translate', 'text-domain-here' );
2. Scan your plugin for strings: - Navigate to WPML > Theme and plugins localization - Select your plugin and click on Scan selected plugins for strings - Wait for the operation to complete 3. Translate the strings: - Go to WPML > String Translation and translate them.
For AJAX-passed text: 1. Declare 'wp-i18n' as a dependency in your JS file:
If this solution does not apply to your case, or if it seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if needed.
Problem: The client is experiencing issues with string translations not working correctly on their WooCommerce site, specifically with page headings/texts that have been added in the WPML String translations settings.
Solution: We identified that the strings in question are managed by a YITH option page, categorized as "Texts in admin screens". Here are the steps we took to resolve the issue: 1. Navigate to WPML > String Translation and click on Translate texts in admin screens at the bottom left of the page. 2. Search for the strings, select them, and click on Add to String Translation. 3. Return to WPML > String Translation to translate the strings into Spanish. The specific strings added were:
[yith_wcmap_endpoint_edit-account]label
(your endpoint label)
[yith_wcmap_endpoint_edit-account]content
(your endpoint content - the h2 title). For further details on registering more fields from this plugin, please refer to the Translating Strings From Admin and Settings section of our documentation.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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: The client needed to migrate or change the language of multiple posts from the default language to another language within a custom post type created using ACF multilingual. Solution: We informed the client that WPML Export and Import can be used to export and import posts into different languages. However, it is necessary to import the posts in the default language first and then import the translations to establish the correct connections between them. We provided the client with documentation links for detailed instructions:
If the provided solution is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also highly suggest checking 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 through the WPML support forum.
Problem: The client needed to display language-specific ACF custom field groups for different languages in LearnDash Lessons and Topics post types. They were encountering an issue where all field groups were displayed irrespective of the selected language.
Solution: 1) We instructed the client to back up their site fully before making any changes. 2) Then navigate to WPML>>Settings>>Post Types Translation. 3) Click on the
Lock
icon for the
Field Groups(acf-field-group)
Post Type. 4) Select the
Translatable - use translation if available or fallback to default language
option for the
Field Groups(acf-field-group)
Post Type. 5) Save the changes. 6)Translate the
TTE Roadmap Branches EN
field group to the secondary languages or creating different
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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. If you still need assistance, please do not hesitate to open a new support ticket with us.
Problem: The client is experiencing a warning message after a WordPress multisite migration indicating that 'WPML is missing some records in the languages tables and it cannot fully work until this issue is fixed.' The client is unable to find the action button/link to 'Clear language information and repopulate languages' on the WPML Troubleshooting page. Solution: 1. We recommend creating a full backup of the site. 2. Check if the tables '
wp_icl_strings
' and '
wp_icl_string_translations
' are present in the database. 3. If the warning persists, navigate to WPML -> Support -> Troubleshooting and click on 'Remove all messages and notifications, for all users.' Alternatively, go to the database >
