Problem: If you're experiencing issues where the CSS breaks on translated pages of your website, it might be related to how global sections are rendered within your theme. Specifically, the Code Snippets plugin may not be loading your theme's CSS correctly for the second language. Solution: We recommend using a Child Theme instead of the Code Snippets plugin. You can add the following snippet to the functions.php file of your Child Theme to address some of the CSS issues:
add_action('init', function() {
// Hook location to output the global section
$location_hook = 'nectar_hook_global_section_footer';
add_action($location_hook, function() use ($location_hook) {
// Detect current language
$current_lang = apply_filters( 'wpml_current_language', null );
// Default section ID (Spanish)
$global_section_id = '24759-2';
// Use translated section ID for English
if ( $current_lang === 'en' ) {
$global_section_id = '26378';
}
// Default category ID (Spanish)
$category_id = 47;
// Use translated category ID for English
if ( $current_lang === 'en' ) {
$category_id = 156;
}
// Output the section only if we're on the correct category archive
if ( is_product_category( $category_id ) ) {
Nectar_Global_Sections_Render::get_instance()->output_global_section($global_section_id, $location_hook);
}
});
});
However, if disabling the Code Snippets plugin resolves all issues, we suggest not using it and instead managing code through the Child Theme as shown above.
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.
Problem: The client is unable to translate a PDF file assigned to a custom 'project' post using an ACF field of type 'file'. The field is set to 'Translate' in WPML settings, but it does not appear in the translation screen, and the same PDF file as the PL version is automatically used for the EN version. Solution: We recommended inserting the following code into the theme's functions.php file to allow translating numeric values, which include the PDF file ID:
After adding this code, make a minor change to the page title and attempt to translate the PDF file ID, which should now be visible in the media library. Additionally, we suggested using the Media Translation interface for a more user-friendly approach to translating the PDF file.
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: The client reported that after translating a property into Greek, the content was missing on the Greek page. Additionally, some fields were still untranslatable. Solution: We advised the client to ensure that the ACF Field Groups were set to 'Not Translatable' in WPML → Settings → Post Types Translation. Then, in ACF → Field Groups → Property Fields, we recommended using the option to apply all fields across languages. For finer control, we suggested switching to 'EXPERT' mode to access field-level options. To address the missing content on the Greek page, the following steps were taken: 1. Edited the property in the default language. 2. Switched to Greek using the language switcher. 3. Scrolled to Theme/Page Options and copied the same settings from English to Greek, ensuring the Content Layout → Post Template was set. 4. Set the custom field 'thegem_page_data' to copy. For the untranslatable fields, we set the specific field 'ammenities' to 'Translate' in ACF Field Groups under 'Expert' mode and updated both the property and its translation.
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 problems persist, please open a new support ticket.
Problem: If you're experiencing issues where the WPML language switcher does not change the language on category or sub-category pages, and it defaults to English despite having translations set up, the issue might be with your custom code. Solution: We found that the 'Product Category Archive Description' snippet is overwriting WPML's permalink rules for categories, which causes the language switcher to malfunction. To resolve this, you can try deactivating the snippet to see if the language switcher then works as expected. If you need the functionality provided by the snippet, consider rewriting it to comply with WPML's multilingual requirements. You can find the necessary guidelines and hooks on our documentation pages:
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 issues persist, please open a new support ticket.
Problem: The client is experiencing issues integrating WPML with a custom funnel plugin (Vamos Funnel) for a multilingual WooCommerce site. The main problems include incorrect loading of translated product data, increased loading times, and mismatched translation strings across different languages.
3. Consider re-architecting the funnel or using a different plugin that has built-in WPML support if integration issues persist. 4. Test the integration on a staging site with minimal setup to isolate issues. 5. If necessary, pivot to a simpler multilingual strategy or a different funnel plugin that is known to work well with WPML.
If these steps do not resolve the issues or if the solution seems outdated or irrelevant 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: Der Kunde versucht, die Sprache des Kunden über den JTL-Connector an das Warenwirtschaftssystem JTL Wawi zu übergeben. Seit den neuesten WPML-Updates funktioniert dies nicht mehr. Zudem zeigt die Validierung bei bereits hinzugefügten Domains an, dass diese nicht gültig seien. Solution: Überprüfen Sie, ob die Variable
$wpmlLanguage
in der Datenbank unter 'wp_wc_orders_meta' vorhanden ist. Verwenden Sie
var_dump($wpmlLanguage);
um zu testen, ob die Variable leer ist. Ersetzen Sie die Bedingung
if ($this->wpml->canBeUsed() && !empty($wpmlLanguage))
durch
if (!empty($wpmlLanguage))
, da die Methode
wpml->canBeUsed()
nicht existiert. Beachten Sie, dass es sich um benutzerdefinierten Code handelt und wir laut unseren Support-Richtlinien beratende Unterstützung anbieten, jedoch keine Verantwortung für benutzerdefinierten Code übernehmen können.
Die Lösung könnte veraltet oder nicht auf Ihren Fall zutreffend sein. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme auftreten, eröffnen Sie bitte ein neues Support-Ticket im WPML Support Forum.
Problème : Le client a rencontré un problème où le lien sur le mot 'Français' redirigeait vers la version anglaise de l'article au lieu de la version française sur son site. Après avoir désactivé le plugin WPML Multilingual CMS, les liens corrects s'affichaient. Solution : Nous avons identifié que le sélecteur de langue utilisé n'était pas celui de WPML mais un modèle personnalisé. Nous avons recommandé d'utiliser le sélecteur WPML, disponible ici : https://wpml.org/documentation/getting-started-guide/language-setup/language-switcher-options/adding-language-switchers-using-php-and-shortcodes/
Pour aligner correctement le sélecteur et le texte, nous avons suggéré d'utiliser le code suivant :
<div style="display: flex; align-items: center;"><span>Lire cet article en</span><div class="wpml-inline-switcher">[wpml_language_selector_widget]</div></div>
De plus, pour corriger les problèmes d'alignement causés par le thème, nous avons ajouté du CSS personnalisé sous WPML > Langues > Options du sélecteur de langue > CSS personnalisé.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de vérifier la version des correctifs permanents 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: The client is experiencing issues with fonts not loading on their English domain and being logged out when switching between their German and English domains using WPML with Elementor.
Solution: 1. Resolve Login Session Issues Across Domains: - Enable Auto Sign-in/Sign-out in WPML → Languages under Language URL format. - Update
2. Address Font Issues on Your English Domain: - Clear all caches (WordPress, Elementor, server, and browser). - Check and adjust Elementor's global typography settings. - Regenerate Elementor's CSS & Data.
3. Increase WordPress Memory Limit: - Edit
wp-config.php
to increase the memory limit:
define( 'WP_MEMORY_LIMIT', '256M' );
If these steps do not resolve the issue or if the solution 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 further assistance is needed, please open a new support ticket at WPML support forum.
