Problem: Wie kann die automatische Übersetzung in einer WPML Entwicklerumgebung mit dem Theme Enfold nachträglich aktiviert werden? Solution: 1. Aktivieren Sie die Option „Alles automatisch übersetzen“ unter WPML > Übersetzungs-Dashboard. Wählen Sie aus, ob neue Inhalte oder auch bestehende Inhalte automatisch übersetzt werden sollen. 2. Oder senden Sie Inhalte über das Übersetzungs-Dashboard zur automatischen Übersetzung. 3. Alternativ kann man die Übersetzung auch selbst automatisch im Advanced Translation Editor anlegen. Dieser kann diese direkt beim Öffnen der Übersetzung auf den gesamten Inhalt anwenden. Im Advanced Translation Editor gehen Sie zu den Einstellungen oben rechts und aktivieren Sie „Alle Inhalte automatisch übersetzen, wenn der Editor geöffnet wird“. Nicht übersetzte Segmente werden automatisch übersetzt, müssen jedoch manuell bestätigt werden. Wichtig: Stellen Sie sicher, dass unter WPML > Übersetzungs-Tools > Automatische Übersetzungs-Engines mindestens eine Übersetzungs-Engine aktiviert ist und dass die richtigen Benutzer unter WPML > Übersetzungs-Tools > Wer kann automatische Übersetzung verwenden? für die Nutzung freigeschaltet sind. Mehr Informationen finden Sie unter:
Falls diese Lösung nicht mehr aktuell ist oder nicht auf Ihr Problem zutrifft, empfehlen wir, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme bestehen, zögern Sie nicht, ein neues Support-Ticket zu eröffnen.
Problem: The client needed to switch the default language of their multilingual site from Spanish to English, but encountered issues with the menu functionality in the translated languages. Solution: We discovered that the template used when clicking the menu icon was not translated into the other languages. This caused the menus in the translated versions to not function properly as they had no templates assigned. After translating the necessary template, the menus started working correctly. If you're experiencing similar issues, we recommend checking that all necessary templates are translated. For further guidance, please refer to our documentation on setting up languages.
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.
Problem: The client is attempting to import WooCommerce products in a secondary language using WP All Import Pro and WPML, but the WPML language selection dropdown is missing from the import interface. Despite following the official documentation and ensuring all necessary plugins and add-ons are active, the dropdown does not appear.
Solution: We recommend the following steps to resolve the issue: 1. Ensure that the "WP All Import - WooCommerce Import Add-On Pro" is installed and active, as this is crucial for importing WooCommerce products. 2. Export your products from the original site in the desired languages. You can export both languages simultaneously or separately. 3. Prepare your CSV files for import. Map the WPML language columns using custom fields as detailed in the documentation: Preparing Import Files for WPML. 4. Import the products using separate CSV files for each language or a combined file for both languages. 5. Run the WPML Export and Import process via WPML → Export and Import.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, we highly recommend checking related known issues at WPML 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 two menu items, 'YDELSER' and 'OM', were not being translated on their English menu despite being translated in the header. The client is using the Gutenkit menu module, which may not follow standard WPML workflows. Solution: We first recommended checking the compatibility of the Gutenkit menu module with WPML and ensuring no hardcoded strings or configurations bypass WPML's translation tools. We advised against repeating standard WPML menu sync or string translation steps as these were already confirmed by the client as ineffective. Instead, we suggested: 1. Inspecting the Gutenkit menu module for specific settings that might require direct translation within its configuration. 2. Using WPML’s String Translation with specific context related to Gutenkit if direct translation within the module is not possible. 3. Ensuring that HTML markers in the Advanced Translation Editor are set correctly, especially for submenu items. This involves copying the original content from the original segment and editing only the text in the translated segment.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Additionally, please 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, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is unsure how to correctly import translated CSV files for WooCommerce products using WPML. They have questions about whether to include the original product in the CSV, whether to check the option to update existing products by SKU/ID, and whether to include SKU or ID in the CSV. Solution: To update products that already have translations, export both the original language products and their translations, make the required changes in the CSV files, and then re-import them. Import the original language CSV first using the option to update existing products by ID or SKU. Then, import the translated CSV, ensuring the correct language is selected in the importer and the update-by-ID or SKU option is enabled. After both imports, run WPML → Export and Import to reconnect the translations and synchronize the updated content. For links within product descriptions, WPML automatically translates internal WordPress links if the linked content has translations. External links need manual translation. For images set as “different per language” in Media Translation, leave the image column unchanged in the translated CSV; WPML will assign the correct language-specific image after the import and synchronization. WPML also offers an option to automate the Export & Import process, which can be helpful for regular updates. More details can be found here: Automate WPML Export and Import Process.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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 with some texts not translating on your block-based cart and checkout page, Solution: We recommend checking the configuration of your translation settings. Ensure that all necessary strings are correctly registered and available for translation in WPML's String Translation interface. If the problem persists, it might be due to a compatibility issue with the current theme or plugin versions. We highly recommend visiting https://wpml.org/known-issues/ to check for any known issues. Also, verify that you have installed the latest versions of your themes and plugins.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket at WPML support forum for further assistance.
בעיה: הלקוח נתקל בבעיה שבה עמוד הבית החדש בעברית לא מוגדר כעמוד הבית באתר והתרגום לאנגלית שלו לא מופיע כראוי. הלקוח רוצה לדעת אם ביטול התרגום לאנגלית של העמוד העברי יאפשר לו לחבר את העמוד האנגלי שהוא רוצה. פתרון: ראשית, עליך להגדיר את עמוד הבית החדש בעברית כעמוד הבית של האתר בהגדרות הכלליות של וורדפרס ב: Settings -> Reading. לאחר מכן, כדי לחבר את העמוד האנגלי כתרגום, עליך לוודא ששני העמודים (העברי והאנגלי) אינם מחוברים כבר לתרגום אחר. ערוך את העמוד עם העורך של וורדפרס ובסיידבר של 'שפה' סמן שהוא תרגום של אף עמוד אחר (NONE). למד כיצד לחבר עמודים במדריך הבא: https://wpml.org/faq/how-to-link-already-translated-pages/. אם הפתרון הזה אינו רלוונטי עבורך, מכיוון שהוא עשוי להיות מיושן או שלא מתאים למקרה שלך, אנו ממליצים לפתוח כרטיס תמיכה חדש. כמו כן, אנו ממליצים לבדוק בדף הבעיות הידועות https://wpml.org/known-issues/, לוודא את גרסת התיקון הקבוע, ולאשר שהתקנת את הגרסאות העדכניות ביותר של התבניות והתוספים.
Problem: If you're unable to see the language selection menu in WP All Import, even though all additional plugins seem to be installed. Solution: We recommend installing the "WPML All Import" addon. You can find this addon in the downloads section of your WPML account or by navigating to Plugins > Add new plugin on the "Commercial" tab. For detailed guidance, please refer to the documentation here. Additionally, be aware of several known issues that might affect your setup:
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is trying to set up WPML to automatically translate all current and future product reviews into English and German. They are specifically looking to configure WPML to recognize and translate new review strings under the domain 'wcml-reviews' automatically. Solution: Currently, only Post Types and Taxonomies can be translated automatically in the background. Strings from WPML > String Translation cannot yet be automatically translated when using "Translate everything automatically". The client will need to create jobs for those strings and send them to be translated automatically. You can even send entire text domains to automatic translation. For more details on translating product reviews, we recommend visiting this guide.
If this solution does not resolve your issue or seems outdated, please 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. If further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
Problem: Der Kunde möchte, dass Übersetzer aus dem Backend heraus benachrichtigt werden können, wenn sie spezifische Seiten überprüfen sollen, auch wenn der Modus "Translate everything" verwendet wird. Derzeit erhält der Übersetzer Benachrichtigungen für alle abgeschlossenen Übersetzungsaufträge, was nicht immer gewünscht ist. Solution: Wir haben bestätigt, dass WPML standardmäßig eine Benachrichtigung sendet, sobald ein Übersetzungsauftrag abgeschlossen ist. Diese Einstellungen können unter WPML > Einstellungen > Übersetzungsbenachrichtigungen gefunden und angepasst werden. Eine spezifische Funktion, die es erlaubt, ausgewählte Benachrichtigungen zu senden, existiert derzeit nicht, aber wir haben die Anfrage intern weitergeleitet, um zu prüfen, ob eine solche Funktion implementiert werden kann.
Bitte beachte, dass diese Lösung möglicherweise nicht relevant ist, da sie veraltet sein könnte oder nicht auf deinen Fall zutrifft. Wir empfehlen dir, 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. Sollte das Problem weiterhin bestehen, zögere nicht, ein neues Support-Ticket zu eröffnen.
Problem: The client encountered an error stating 'There was an error processing your order. Please check for any charges in your payment method and review your order history before placing the order again.' This issue was due to not meeting the minimum server requirements for WPML. Solution: We recommended increasing the WordPress memory limit to at least 256 MB, as WPML requires a minimum of 128 MB. The client's current WordPress memory limit was only 40 MB, despite having a PHP memory limit of 1024 MB. To resolve this, the client needed to: 1. Connect to their website's server and open the
wp-config.php
file located in the WordPress root directory. 2. Add the following line of code to increase the memory limit:
define('WP_MEMORY_LIMIT', '256M');
This code should be added just before the comment:
// That's all, stop editing! Happy blogging.
3. Check the current values under WPML > Support > WordPress. If the hosting provider restricts these settings, we advised contacting them to make the necessary changes. Additionally, we suggested clearing the site's cache and temporarily deactivating any snippets in WPCode Lite for testing purposes. If these steps do not resolve the issue, we recommend visiting our known issues page and verifying the version of the permanent fix. Ensure that the latest versions of themes and plugins are installed. If the problem persists, please open a new support ticket.
