Compatibility

Problem:
You are working on a multilingual site using WooCommerce along with Barn2 Wholesale Pro and Barn2 Product Tables, and you're facing an issue where the WPML flags on the wholesale store page redirect users to the public shop page instead of the wholesale store page.
Solution:
We have identified this as a potential compatibility issue between WPML and Wholesale Pro. To address this, we need to replicate the issue on a clean installation.
1. Install Wholesale Pro.
2. Add a sample product and translate it.
3. Add a wholesale user.
4. Set the archive page for wholesale.
5. Try to replicate the issue.
This process will help us report the issue to our compatibility team and expedite finding a solution.

If this solution becomes irrelevant due to updates or if it does not apply to your case, we highly recommend 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 the issue persists, please open a new support ticket.

Problem:
You need to translate email strings into Estonian using the Kadence Email Customizer plugin while keeping placeholders like {invoice_pay_link} functional.
Solution:
We recommend adding specific code to the functions.php file of your child theme to handle the translation and functionality of placeholders. Here are the steps:

1. Add the following code to handle the translation and dynamic replacement of the {invoice_pay_link} placeholder:

   add_filter('kadence_woomail_order_body_text', function($body_text, $order, $sent_to_admin, $plain_text, $email){<br />    if (class_exists('WCML_Orders')) {<br />        $key = $email->id;<br />        $btn_switch = Kadence_Woomail_Customizer::opt($key . '_btn_switch');<br />        $pay_link = "";<br />        if ($order->get_checkout_payment_url()) {<br />            if (true == $btn_switch) {<br />                $pay_link = '<p class="btn-container"><a class="btn" href="' . esc_url($order->get_checkout_payment_url()) . '">' . esc_html__('Pay for this order', 'kadence-woocommerce-email-designer') . '</a></p>';<br />            } else {<br />                $pay_link = '<a href="' . esc_url($order->get_checkout_payment_url()) . '">' . esc_html__('Pay for this order', 'kadence-woocommerce-email-designer') . '</a>';<br />            }<br />        }<br />        $body_text = str_replace('{invoice_pay_link}', $pay_link, $body_text);<br />        $site_title = get_bloginfo('name');<br />        $body_text = str_replace('{site_title}', esc_html($site_title), $body_text);<br />        $order_language = $order->get_meta('wpml_language');<br />        $body_text = apply_filters('wpml_translate_single_string', $body_text, 'admin_texts_kt_woomail', $key.'_body', $order_language);<br />    }<br />    return $body_text;<br />}, 20, 5);

If this solution does not resolve your issue or seems outdated, please check the related known issues 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 with us for further assistance.

Problem:
If you're experiencing issues where the menu bar on your French pages scrolls over the text, or when edits made to a page cause loss of format settings on the translated page, we have identified solutions.
Solution:
For the issue of losing format settings after translating edits, we recommend adjusting the translation settings for your Advanced Custom Fields (ACF). Specifically, navigate to ACF > Field Groups and locate the 'Hero 1' field group. Change the translation preference to 'Expert' mode at the top of the page. Then, find the 'settings' custom field and set the 'Translation preferences' to 'copy'. After making these changes, return to the original version of your page, make any necessary edits, and update it. This should ensure that the settings carry over correctly when the page is retranslated.

If these solutions do not resolve your issues, or if they seem outdated, please check the related known issues 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 with us for further assistance. You can do so at WPML support forum.

Problem:
Du arbeitest mit dem 'Contest Gallery' Plugin und hast festgestellt, dass einige Texte für die Anmeldemaske und die Kategorien nicht in den Übersetzungs-Strings von WPML erscheinen. Trotz Aktivierung der Option 'Nicht übersetzte Zeichenketten erkennen' und dem Versuch, die Strings zu synchronisieren, sind die Texte nicht auffindbar.
Solution:
Das 'Contest Gallery' Plugin, insbesondere die kostenlose Version, ist nicht vollständig nach den Internationalisierungsstandards von WordPress programmiert, was zu Problemen mit WPML führt. Das Plugin registriert keine benutzerdefinierten Felder in den WPML-Einstellungen und verwendet fest codierte Zeichenfolgen ohne konsistente Textdomänen. Außerdem werden beim Übersetzen keine neuen Galerien angelegt, was bedeutet, dass die IDs der Galerien in verschiedenen Sprachen nicht übereinstimmen. Eine Lösung könnte sein, die Pro-Version des Plugins zu verwenden, falls diese anders programmiert ist. Alternativ könnten die Plugin-Autoren unser Go Global-Programm in Anspruch nehmen, um die Kompatibilität zu verbessern.

Falls diese Lösung für dich irrelevant ist, weil sie veraltet ist oder nicht auf dein Problem zutrifft, empfehlen wir dir, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version des permanenten Fixes zu verifizieren und zu bestätigen, dass du die neuesten Versionen von Themes und Plugins installiert hast.

Problem:
The client is unable to see the full text for translation in WPML, coming from Spectra blocks, and the translated text does not appear on the frontend for their product descriptions.

Solution:
1) We added necessary XML configurations for Gutenberg blocks in WPML -> Settings -> Custom XML Configuration to make them translatable. Here is the XML needed for some of the blocks:

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="uagb/tabs" translate="1">
      <key name="tabHeaders"></key>
      <xpath>//div/ul/li/a/div</xpath>
    </gutenberg-block>
    <gutenberg-block type="uagb/tabs-child" translate="1">
      <key name="header"></key>
      <key name="tabHeaders"></key>
    </gutenberg-block>
    <gutenberg-block type="uagb/faq-child" translate="1">
      <key name="question"></key>
      <key name="answer"></key>
    </gutenberg-block>
    <gutenberg-block type="uagb/advanced-heading" translate="1">
      <xpath>//div/p</xpath>
      <xpath>//div/h3</xpath>
      <xpath>//div/h4</xpath>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

2) We translated several related "Patterns" and "Content Blocks" via WPML -> Translation Management. After assigning the translation tasks, we completed them from the "Translation queue".
3) For any untranslated blocks, such as product tabs, additional XML paths were added, and a minor change in the original content was made to update the translations.

If this solution does not resolve your issue, 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 the problem persists, please open a new support ticket.