Custom Work

Problem:
You are using WPML with WooCommerce and WooCommerce Bookings, and you want all outgoing emails to be delivered only in the default language, English. However, customers are receiving booking and order emails in various languages, such as English, German, or Dutch, even when they order the same product in English.
Solution:
Currently, there is no straightforward out-of-the-box solution to ensure all outgoing emails are sent only in English, as emails are typically sent in the language in which the order was made or the language set in the user's profile. We recommend translating the emails and setting the default language as English in the translations. Alternatively, you could consider hiring a contractor to implement custom code to achieve this functionality. You can find qualified contractors at https://wpml.org/contractors/.

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.

Problem:
You are trying to translate a dynamically populated ACF field using the ACFML plugin, but the field is not translating or appearing in the other language.
Solution:
1. Verify that your ACF Select Field has Choices set. If no Choices are declared, WPML cannot translate them using the WPML Translation Editor because the values are set through custom code.
2. To translate such fields, use the WPML String Translation. You can register the strings for translation using a GetText call in PHP or by utilizing the WPML hook: https://wpml.org/wpml-hook/wpml_register_single_string/
3. For additional guidance on translating themes and plugins you've created, refer to: https://wpml.org/documentation/support/translating-the-theme-you-created/

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: WPML Support Forum.

Problem:
The client wants to translate custom post type (CPT) slugs without using WPML's String Translation, aiming for a cleaner approach while maintaining language-specific URLs (e.g., English: example.com/en/products/, German: example.com/produkte/). They are experiencing issues with 404 errors and incorrect language detection in requests.
Solution:
We recommend using WPML's String Translation for translating CPT slugs as it is a mandatory plugin for such functionality. Ensure that the 'has_archive' is set to true in your code, as shown below:

WPML supports custom slug translation when the custom type is registered but does not support custom permalink structures. For more details, please refer to our documentation on translating slugs for custom post type archives.
If you require a custom solution, we suggest using the services of WPML contractors, which can be found here: WPML contractors.

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 at WPML support forum.

Problem:
You are using WPML to manage a multilingual site and need to set up permissions so that translators can only view the original language content and edit their assigned language translations. You are looking for a way to make the original content 'view-only' and inquire about any available WPML filters or hooks to implement these restrictions.
Solution:
The client has managed to achieve it using custom code on his own.
Please note that the solution might be 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.

Problem:
You are trying to display all posts in all languages on a US page using WPML, but the default WPML settings do not support this functionality.
Solution:
We recommend adjusting your query to bypass WPML's default language filtering. Here's how you can modify your WP_Query:

Please note that this solution is a custom workaround and was not extensively tested. If this solution does not work or seems outdated, or if it does not apply 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:

The client is experiencing an issue where editing a job post in one language results in updates being saved across all language versions, leading to prolonged save times. They seeks a solution to save the job in the original language without automatically updating all the language versions immediately.

Solution:

We informed that due to the nature of WPML and its handling of duplicated posts, any updates to the original post would automatically sync with the duplicates. To manage this, the client can manually set the duplicates to 'Translate Independently' by clicking the Translate Independently button on the duplicate post in the secondary language. This action prevents automatic updates to the translated versions when the original is edited. Later, if needed, the translated versions can be updated manually by selecting the Overwrite with - option.

For detailed steps, please refer to the following documentation:

• Editing Duplication
• Translate Independently
• Using Different Translation Editors for Different Pages

If this solution does not apply or is outdated, we 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 is experiencing an issue where widget names on a bilingual site (Lithuanian and Russian) are not displaying correctly in Russian, despite using WooCommerce Multilingual & Multicurrency and WPML's string translation. The widget names remain in Lithuanian for both languages, although attribute names display correctly.
Solution:
First, we suggested manually translating the widget and ensuring that the translated version selects the corresponding translated term. This guide provides detailed steps: Translating Widgets.
Next, we advised resaving each Block Widget under "Appearance > Widgets" to potentially register the strings for translation. If this did not resolve the issue, it indicated that these Block Widgets might not support WPML, requiring manual string registration as outlined here: Translation for Texts by Other Plugins and Themes.
Upon further investigation, it was discovered that the latest WooCommerce filter widget block does not recognize translated attributes. We recommended using the Legacy Filter Attribute block instead, which should display attribute names correctly in each language. Custom CSS was also applied to address display issues with the filter.

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.