Problem: The client reported that the Bricks Builder blog template layout was not displaying correctly in translated versions, despite multiple updates to the translation. The issue persisted even after creating separate templates for each language and manually connecting them. Solution: We investigated the issue and found that it was related to the translation settings in WPML. Specifically, the settings under WPML > Settings > Custom Field Translation had been modified. To resolve the issue, we recommend: 1. Reverting the translation settings to match those on our sandbox site. 2. Resaving the original template and its translations. Please ensure to back up your site before making these changes.
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 is using LightspeedHQ to manage stocks between their physical store and WooCommerce webshop, which has been translated into English and German using WPML. They noticed that orders placed on the translated versions of the site are not being synced to the LightspeedHQ system. This issue arises because WPML creates duplicates of products for each translation, each with different product IDs, which LightspeedHQ does not support. Solution: We suggested verifying the REST API responses from the client's website to ensure they are correct and can be retrieved properly in both languages. We recommended exploring the use of a dedicated plugin that supports WPML and can handle translated products. Two potential plugins to consider are:
If these plugins do not resolve the issue, we advised checking with the plugin authors to confirm whether their solutions support the needed functionality and how they process the data. Additionally, we confirmed that WPML's behavior of creating new product IDs for translations is standard and cannot be adjusted.
If this solution does not apply or is outdated, we recommend opening a new support ticket. We also highly suggest 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 at WPML Support Forum.
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.
בעיה: הלקוחה נתקלה בבעיה בעת עדכון תמונות בשדות גמישים באמצעות WPML, כאשר השדות אינם מעדכנים כראוי לאחר העתקה ראשונית. פתרון: 1. יש לוודא שהאפשרות לעורך התרגום המתקדם של WPML מופעלת, וניתן להחליף לעורך תרגום של וורדפרס אם נדרש. 2. יש לבדוק אם תוסף כגון Classic Editor או תוסף בונה עמודים מבטל את עורך הבלוקים של וורדפרס. 3. יש להגדיר את השדה הגמיש ושדה התמונה ל'העתק פעם אחת' על פי המדריך של WPML לשדות מותאמים אישית: מדריך לתרגום שדות מותאמים אישית ב-WPML. 4. יש לוודא שכל התוספים והגרסאות מעודכנים לגרסתם האחרונה.
אם הפתרון המוצע אינו רלוונטי עקב עדכונים או שהבעיה שלך שונה, אנו ממליצים לפתוח כרטיס תמיכה חדש. כמו כן, מומלץ לבדוק את עמוד הבעיות הידועות ב-WPML כאן ולוודא שהתקנת את הגרסאות העדכניות ביותר של התוספים והערכות.
Problem: Wenn du feststellst, dass Übersetzungen für benutzerdefinierte Module von Bricksable, die mit ATE übersetzt wurden, nicht im Frontend gerendert werden, Lösung: Wir empfehlen, bestimmte Codezeilen in der Datei
Diese Änderungen sollten das Problem für das "Content Toggle"-Modul beheben. Für andere Module mit dem gleichen Problem solltest du denselben Ansatz verwenden (Ersetzen der Unterstriche durch Bindestriche).
Bitte beachte, dass diese Lösung möglicherweise veraltet oder nicht auf dein Problem zutreffend ist. Wir empfehlen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass du die neuesten Versionen von Themes und Plugins installiert hast. Wenn das Problem weiterhin besteht, zögere nicht, ein neues Support-Ticket zu eröffnen.
Problem: The Arabic version of your website was displaying a maintenance page instead of the expected content. This issue was due to incorrect settings in the Strings Translation for the Tutor Maintenance Mode. Solution: We resolved the issue by adjusting the Strings Translation settings. Specifically, the value for the string named
[tutor_option]enable_tutor_maintenance_mode
was incorrectly translated from 'off' in English to 'على' in Arabic. We corrected this by removing the incorrect translation and copying 'off' into the Arabic translation. This change fixed the problem, and the Arabic homepage should now display correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
