Problem: The client wants to configure the WPML language switcher to appear as a simple icon in the header, similar to the design used by Weglot, with specific features such as a small flag icon with the language abbreviation, visible directly in the header, and a dropdown menu that appears on hover without requiring a click. Solution: We recommend using the manual mode for customizing the WPML language switcher. This mode allows for specific design adjustments that are not typically available through standard WPML settings. For detailed guidance on implementing manual mode, please refer to our documentation: Using Different Translation Editors for Different Pages.
If this solution does not fully address your needs, or if it seems outdated or not applicable to your 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. Should you require further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is working on a multilingual project using ACF Options Pages and is facing issues with translating them. They want each language version of the ACF Options Pages to behave like regular posts in WPML, with each having its own version and linked as translations of each other without affecting the content of another language when one is saved.
Solution: We explained that ACF Options Pages behave differently with WPML and cannot be edited directly via the WordPress admin editor. The correct process involves: 1. Setting up the options page in ACF. 2. Populating the values via WordPress admin. 3. Translating the page via WPML > Translation Dashboard. For more detailed guidance, we recommend checking the documentation on translating sites built with ACF, specifically for ACF Options Pages at https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#acf-options-pages.
If this solution does not resolve your issue or seems outdated, please open a new support ticket. We also 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, you can contact us directly through the WPML support forum.
Проблема: Клиент хочет включить создание версии на русском языке для кастомного типа записи togo_trip. Решение: 1. Перейдите в WPML → Settings → Post Types Translation. 2. Найдите тип записи togo_trip. 3. Установите для него опцию Translatable – only show translated items. 4. Сохраните изменения. После этих шагов записи данного типа можно будет корректно переводить и отображать на соответствующих языках. Подробнее об этом можно прочитать в нашей документации: https://wpml.org/documentation/getting-started-guide/translating-custom-posts/
Если данное решение окажется неактуальным или не подходит под ваш случай, мы рекомендуем открыть новый тикет поддержки. Также рекомендуем проверить связанные известные проблемы на https://wpml.org/known-issues/, убедиться в версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
Problem: You are using WPML with WooCommerce, Elementor, and the XStore theme and want to translate product category names into Arabic while keeping the products only in English. However, when you translate a product category into Arabic, it shows 0 products in the category carousel on the Arabic version of the site. Solution: First, ensure that you have translated all product categories by creating a dummy product, assigning all categories to it, and sending it for translation. For more details, visit https://wpml.org/faq/how-to-translate-all-taxonomy-terms-at-once/.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client translated the footer template using Elementor into Italian and Spanish, but the English version continued to display on the multilingual site. Additionally, the flags for language switching were not appearing on the menu. Solution: We identified that the issue was due to the same Elementor template ID being used across all languages, which was stored in the Customizer setting (footer_template). To fix this, we: 1. Went to WPML → String Translation → Admin Texts and searched for the default language Elementor template ID (589), then added this option for translation. 2. Returned to String Translation and set the ID of the translated Elementor template for the secondary language. This adjustment allowed WPML to load the correct footer template for each language. For further guidance on translating theme options, you can visit our documentation here: https://wpml.org/documentation/getting-started-guide/string-translation/how-to-translate-theme-options/
If this solution does not resolve your issue or seems outdated, we 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: Nach der Migration der Website von mugarecycling.com zu muga.ch können einige Seiten wie 'Impressum' und 'Aktuell' nicht übersetzt werden. Es erscheinen Fehlermeldungen, dass WPML die Seite dreimal zu übersetzen versucht hat und gescheitert ist, sowie kritische Fehler aufgrund von Speicherproblemen. Solution: 1. Wenn ein Übersetzungsauftrag vor der Migration noch in Bearbeitung war, sollten Sie den originalen Inhalt bearbeiten, die Seite erneut speichern und dann die Übersetzung durchführen. Sollte dies nicht helfen, brechen Sie den aktuellen Auftrag ab und beginnen Sie erneut. Weitere Informationen finden Sie hier: https://wpml.org/de/faq/translation-status-stuck-or-displaying-the-error-wpml-didnt-manage-to-translate-this-page/ 2. Erhöhen Sie das PHP MEMORY LIMIT auf Ihrem Server und in der WordPress-Konfiguration auf mindestens 256M, um Speicherprobleme zu vermeiden.
3. Fügen Sie folgende Zeilen in Ihre wp-config.php ein, um auch das WP MEMORY LIMIT zu erhöhen:
Überprüfen Sie die aktuellen Werte unter WPML > Support.
Falls diese Lösungen Ihr Problem nicht beheben oder nicht zutreffen, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Überprüfen Sie auch die bekannten Probleme, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support-Forum.
Problem: Der Kunde möchte, dass die übersetzten Seiten im Avada Theme die gleiche Formatierung wie die Originalseiten behalten. Es gibt Probleme mit der automatischen Umformatierung und der Definition des originalen Inhalts. Solution: 1. Um die Theme-Optionen für alle Sprachen gleichzeitig zu setzen, sollte man in den Avada-Theme-Optionen die Sprache in der oberen Admin-Leiste auf "Alle Sprachen" umstellen. Weitere Informationen finden Sie hier: Wie man Theme-Optionen für Sprachen in Avada setzt. 2. Um den deutschen Inhalt als Original zu definieren und die Formatierung zu behalten, muss eine Anpassung vorgenommen werden, nachdem eine Sicherungskopie der Website erstellt wurde. Danach kann der Inhalt im WPML-Übersetzungseditor neu übersetzt werden. 3. Um bereits übersetzte Seiten zu verbinden oder die Verbindung aufzuheben und neu zu definieren, welche Sprache die Ausgangssprache sein soll, folgen Sie dieser Anleitung: Wie man bereits übersetzte Seiten verbindet.
Falls diese Lösungen veraltet sind oder nicht auf Ihr Problem zutreffen, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Überprüfen Sie auch die bekannten Probleme, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: If you're trying to manually install WPML plugins and encounter the error message 'The link you followed has expired. Please try again', or if you need guidance on installing the plugin using FTP, we can help. Solution: First, ensure you have a backup of your website. It's safer to perform these operations on a staging version of your site to prevent any disruptions. Here are the steps to manually update or install WPML: 1. Sign in to your WPML account at https://wpml.org/account/downloads/. 2. Download the latest versions of WPML and its add-ons. 3. If using FTP, unzip the downloaded files to access the plugin folders. Connect to your site via FTP, navigate to public_html → wp-content → plugins, delete any existing WPML plugin folders, and upload the new ones. 4. After uploading, go to your WordPress Dashboard → Plugins and activate WPML. For automated updates, you can check for updates directly from your WordPress dashboard under Plugins > Add New > Commercial tab. For more detailed instructions on manual updates, visit https://wpml.org/faq/updating-wpml-manually/. To provide debug information for further support, follow the steps at https://wpml.org/faq/provide-debug-information-faster-support/.
If this solution does not apply to your situation, 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's website is originally in English and translated into German using WPML. When a contact form is submitted from the German site, the redirect thank you page appears in English, the confirmation email is sent in English, and the form data pulled by Zapier is from the English form, despite having the direct link for the German thank you page set in the redirect. Solution: We recommended the client to first ensure that all WPML plugins are up to date by following these steps: 1. Create a backup of the website. 2. Navigate to WordPress Dashboard > Plugins > Add new > Commercial (tab). 3. Click the Check for Updates button. 4. Update WPML and its addons. For more information on automated updates, visit https://wpml.org/faq/install-wpml/#automated-updates Next, we asked the client to confirm if they used the Elementor Form widget and whether the thank you message was also translated during the setup. Additionally, we advised enabling the Ajax language feature to support proper language redirection, which can be set up by following the instructions at https://wpml.org/documentation/getting-started-guide/language-setup/enabling-language-cookie-to-support-ajax-filtering/
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your 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: One item in the main menu, specifically for the 'product section', was not translated. Solution: We resolved this issue by syncing the menus correctly using the WPML > WP Menu Sync option. If you're experiencing this issue, we recommend you try the same steps. For detailed guidance, follow the steps in the WPML menu translation documentation.
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: You do not have permission to view pages related to the WPML plugin. Solution: If you're experiencing this issue, we recommend following the steps outlined in the WPML forum post. It appears that the capabilities were not set correctly. By resetting them as described in the post, the issue should be resolved. You can find the detailed instructions here: WPML forum topic on access permissions.
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 wants to complete the automatic translation of their website into French using DeepL for the remaining content, and ensure future content is also automatically translated. They are also unsure about the credit requirements and purchasing options for DeepL. Solution: 1. Set DeepL as the default translation engine by navigating to WPML > Settings > Automatic translation, selecting "Different Engine", ensuring DeepL is activated, and placing it first in the list. 2. To estimate the translation credits needed, go to WPML > Translation Dashboard, filter for "Not completed" translations, select all, and choose "Translate automatically" for all languages. This will provide a credit estimate using DeepL. 3. To automatically translate future content, after completing steps 1 and 2, activate "Translate Everything Automatically" in WPML > Translation Dashboard, with the option to select only future content for automatic translation. For more details, visit Translate Everything Automatically.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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.
