Compatibility

Problem:
If you're experiencing issues with the Divi Woo Products module not filtering by category on translated pages in Divi 5, where the module displays all products instead of the selected category, this might be due to WPML not correctly passing the language context to the Divi 5 module.
Solution:
First, try manually selecting the correct product category in the Woo Products module while the admin language is set to the language of the page you are editing. This workaround involves editing the translated pages directly rather than using the WPML Translation Editor.
If the issue persists, we recommend adding a custom XML configuration to your WPML settings. Here's how:
1. Navigate to your WordPress Dashboard > WPML > Settings > Custom XML Configuration.
2. Add the following code:

<wpml-config><gutenberg-blocks><gutenberg-block type="divi/shop" translate="0"><key name="content"></key><key name="advanced"></key><key name="includeCategories"></key><key name="*"></key><key name="value"><key name="*" type="taxonomy-ids" sub-type="product_cat"></key></key></gutenberg-block></gutenberg-blocks></wpml-config>

3. After adding the code, make a minor edit to the original page and save it. This should prompt an update for the translations.
4. Re-edit the translations to ensure they are 100% complete and save.

Please note that this solution might become irrelevant due to updates or may 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 the problem persists, please open a new support ticket at WPML support forum.

Problem:
The client set a new homepage using SiteOrigin Premium and configured it as a static page in WordPress settings. However, the new homepage does not display the layout built with SiteOrigin, showing instead the layout of the old homepage without a sidebar.
Solution:
We determined that the issue is not related to WPML. Here are the steps we took to diagnose the problem:
1. Temporarily deactivated WPML to ensure the issue was not related to the translation plugin.
2. Set the new homepage as a static page in the original language under Settings → Reading.
3. Found that the homepage still did not display the SiteOrigin layout, even with WPML deactivated.
Since the problem persists without WPML, it suggests that the issue is related to either the theme or SiteOrigin itself. We recommend contacting SiteOrigin support for further assistance.

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

Problem:
If you're experiencing issues where links within the 'Essential Addons for Elementor' plugin redirect to the main language page instead of staying on the current language, and you need to click twice to navigate back, we have a solution for you.
Solution:
First, ensure you have a full backup of your site. Then, add the following code to your theme’s functions.php file:

add_filter( 'elementor/frontend/before_render', 'wpml_compsupp8345_eael_wrapper_link');<br />function wpml_compsupp8345_eael_wrapper_link( $element ) {<br />    if ( 'container' !== $element->get_data( 'elType' ) ) {<br />        return;<br />    }<br />    $settings = $element->get_settings();<br />    if ( empty( $settings['eael_wrapper_link']['url'] ) ) {<br />        return;<br />    }<br />    $lang = apply_filters( 'wpml_current_language', null );<br />    $url  = apply_filters( 'wpml_permalink', $settings['eael_wrapper_link']['url'], $lang, true );<br />    $settings['eael_wrapper_link']['url'] = $url;<br />    $element->set_settings( 'eael_wrapper_link', $settings['eael_wrapper_link'] );<br />}

After implementing this code, clear any cache that might be affecting your site. This solution dynamically adjusts the URLs based on the current language, ensuring that links do not revert to the default language.

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 problems persist, please open a new support ticket.

Problem:
Die URL des Site Logo Widgets von Ultimate Addons for Elementor wird nicht übersetzt.
Solution:
Wir empfehlen Ihnen, auf die neueste Version von Ultimate Addons for Elementor zu aktualisieren, da das Problem in Version 2.8.7 behoben wurde. Sollte das Problem weiterhin bestehen oder die Lösung aufgrund von Aktualisierungen irrelevant geworden sein, überprüfen Sie bitte die bekannten Probleme und stellen Sie sicher, dass Sie die neuesten Versionen Ihrer Themes und Plugins installiert haben. Wenn dies nicht hilft, eröffnen Sie bitte ein neues Support-Ticket.
Wir empfehlen Ihnen dringend, ein neues Support-Ticket zu eröffnen, falls das Problem weiterhin besteht. Besuchen Sie unser Support-Forum für weitere Unterstützung.

Problème :
Vous cherchez vos formulaires dans le tableau de bord de traduction, mais la liste reste vide malgré l'activation des extensions nécessaires et l'utilisation du menu "envoyer à la traduction". Vous pouvez trouver les chaînes dans le traducteur de chaînes mais préférez une méthode plus intuitive.
Solution :
Nous avons identifié que le problème est lié à la table de base de données

icl_string_packages

: il manque une colonne intitulée

translator_note

. Nous avons mis à jour manuellement cette table dans une copie locale, ce qui a permis d'afficher les formulaires comme prévu dans le tableau de bord de traduction. Nous vous recommandons de faire une sauvegarde de votre site et de nous confirmer pour que nous puissions effectuer ces modifications sur votre site en ligne.

Si cette solution devient obsolète ou si elle ne correspond pas à votre cas, nous vous recommandons vivement de consulter les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.

Problem:
If you're experiencing an issue where your event dates are displaying as '1 January 1970' instead of the actual start and end dates on your website using the Avada theme, this might be due to a conflict with WPML.
Solution:
We recommend the following steps to address this issue:
1. Ensure you have a backup of your website.
2. Add the following code to your theme's functions.php file:

/* Workaround for compsupp-8340 */<br />add_filter( 'fusion_set_dynamic_params', function( $params ) {<br />    if ( isset( $params['event_date']['callback']['function'] ) ) {<br />        $params['event_date']['callback']['function'] = 'wpml_compsupp8340_fix_avada_event_full_date';<br />    }<br />    return $params;<br />}, 20 );<br /><br />function wpml_compsupp8340_fix_avada_event_full_date( $args, $post_id = 0 ) {<br />    // Function implementation here<br />}

3. Test this solution in a staging environment before applying it to your live site to ensure it does not cause other issues.

Please note that this solution might become irrelevant due to updates or may not apply to your specific case. If this solution does not resolve your issue or if you encounter other problems, 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, feel free to open a new support ticket at WPML support forum.