Problem: The client is experiencing issues with large MySQL data tables due to the 'Translate Everything Automatically' feature in WPML, which is translating more content than necessary. The client is also unable to exclude specific post types from being translated and is concerned about the increased costs and database size.
Solution: Our developers are aware that WPML's tables can grow to a huge amount of data and they are looking into optimizing the dataflow in WPML 4.8. Further, in case you need more control about what should be translated in which way, we recommend disabling the 'Translate Everything Automatically' option. This can be done at WPML > Translation Management > Dashboard on the top right. By disabling this option, the client can manually select which content to translate or assign it to other translators. For further guidance on managing translations, we suggest reading this guide: https://wpml.org/documentation/translating-your-contents/.
If the solution provided does not resolve the issue or seems outdated, or if it does not apply to your specific case, please open a new support ticket. 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, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are developing a site and encounter an issue where Plugin Notes Plus stops working when the WPML main plugin is activated. The specific error in the console is:
Uncaught TypeError: Cannot read properties of undefined (reading 'replace')
at various points in the Plugin Notes Plus JavaScript files. Solution: The Plugin Notes author released a fix for this issue.
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 at WPML support forum for further assistance.
Problem: The client is developing a site and wants to set up automatic translation for WooCommerce elements such as orders, refunds, posts, and subscriptions. They also want to ensure that all frontend elements, including multilingual emails, are translated correctly. Solution: We recommended checking our WooCommerce Multilingual & Multicurrency guide for general setup and specifically our guide on how to translate WooCommerce emails for email translations. For subscription products, we provided a guide to ensure correct translation setup: Translating WooCommerce Subscriptions. We clarified that actual subscriptions should not be translated as the client will only have one subscription regardless of the language.
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 this does not resolve your issue, please open a new support ticket.
Problem: You are developing a site using GeneratePress blocks in the Gutenberg editor and encountering issues while creating a list. The translation process mixes the strong tag, leading to a design break. Solution: We recommend creating a new test page and translating it to see if the markers are added correctly. This step will help determine if the issue is related to the page's size or another factor.
If this solution does not resolve your issue or 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. Should these steps not provide a resolution, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: The client experienced a significant increase in the size of the icl_translation table after switching from Elementor to Gutenberg/GeneratePress, causing delays in staging software due to the large database size. The client also inquired about the creation and loading of .mo files for translations. Solution: We can offer installing a special plugin to manage and delete unnecessary jobs that may be enlarging the database. Our developers are aware of this issue and are working on a solution in a future version of WPML.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
Problem: You have four profile types in Buddyboss and have set profile types to translation in the settings and translated them. However, in the profile type dropdown list, all different profile types are shown instead of only the ones in the chosen language, and their text has no color. Solution: We are aware of this issue and our developers have added it to the backlog. The main challenge lies in handling this when the data is not available in a standard WordPress CPT format. A new version of Buddyboss glue has been released which addresses this issue. We recommend updating to this latest version.
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 the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: You are working on a site under development and trying to add a string for translation in a child theme custom template using the code:
printf( __( '<a href="%s">Secure your login with Two-Factor Authentication (2FA) and Passkeys</a>', 'buddyboss' ), esc_url( '/account-security/' ) );
However, the string cannot be found for translation. Solution: We recommend checking if the 'Auto register untranslated strings' option is enabled, as it should register new strings by default. Additionally, for custom coding scenarios, you might need to scan the theme or plugin files. You can do this through WPML-> Theme and plugins localization.
The 'Auto register untranslated strings' option registers the untranslated strings while visiting the site and adds them to String Translation. The 'Track where strings appear' feature helps identify the source and location of the strings on the site.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket.
Problem: If you're experiencing issues where old content that no longer appears on your page is still visible in the Advanced Translation Editor after switching from Elementor to Generatepress Blocks, this summary might help. Solution: We recommend switching to the WordPress editor on the affected page and then switching back to the WPML Translation Editor. This action should help in removing the outdated main content from the editor.
Please note that 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
