Custom Work

Problem:
If you're using

apply_filters('wpml_copy_post_to_language')

to create translations of products and find that it does not copy product attributes, you might encounter difficulties in achieving complete product translations.
Solution:
First, ensure that in WPML > Settings, under Taxonomy translation, the translation preference for Attributes is set to "Copy". If this does not resolve the issue, you can manually copy product attributes using custom code. Here's a step-by-step guide:
1. Create an independent translation of the post in the target language using

$translated_post_id = apply_filters('wpml_copy_post_to_language', $product->get_id(), $target_language, false);

2. Retrieve the translated product with

$translated_product = wc_get_product($translated_post_id);

3. Get attributes from the original product with

$attributes = $product->get_attributes();

4. Set these attributes to the translated product with

$translated_product->set_attributes($attributes);

5. Save the translated product with

$translated_product->save();

If you need further customization, consider hiring a developer from 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:
The client is experiencing an issue where a SQL query sorts posts by a custom meta field 'trainings_display_date_start' on the homepage. This works correctly on the non-translated (English) page, but not on the translated page, resulting in no posts being returned.
Solution:
1. Ensure that the 'trainings_display_date_start' is copied over to the translated posts so there is meta data to sort by.
2. Include a meta query that returns only posts with a start date and then sort by that start date.
3. Verify that the posts are translated and published in the second language.
4. Test the issue with the WP default theme and only WPML plugins enabled to see if the issue is caused by something else.

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 contact our support forum at WPML support forum.

Problem:
You are trying to display a translated profile field in a different section than the default Profile section on your website. Specifically, you have moved the field to the 'Profile header' using custom code, but the field displays in English instead of the selected language.
Solution:
To ensure the field displays in the correct language, you should use the

wpml_translate_single_string

hook instead of the

wpml_object_id

filter, as the latter is intended for filtering post types by ID. Here is how you can modify your code:

function render_member_header() {<br />  $expertise = xprofile_get_field_data('My Offer', bp_displayed_user_id(), 'comma');<br />  echo '<span>'. apply_filters('wpml_translate_single_string', $expertise, 'context', 'name') .'</span>';<br />}<br />add_action('bp_before_member_header_meta', 'render_member_header');

For more details on using this hook, please visit wpml_translate_single_string documentation.

If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum.