Problem: If you're trying to translate the content of the "Divi Pixel FAQ" module and can't find the strings anywhere, we recommend following these steps. Solution: 1. Navigate to WPML >> Settings > Post Types Translation. 2. Set the FAQ or “dipi_faq” post type to "Translatable - only show translated items". 3. You should now be able to translate the FAQ post type posts as normal posts/pages. For more details, check out our documentation on translating custom posts. If the issue persists, please add the debug report in the Debug Information box. You can find instructions on how to provide this information here: provide debug information for faster support.
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 this does not resolve your issue, please open a new support ticket.
Problem: The client was new to the tool and attempted to translate their content into 12 languages simultaneously, using up their 60000 translation tokens. After realizing the cost, they deleted the translations and inquired about the possibility of getting their tokens refunded. Solution: We informed the client that translation credits are non-refundable once purchased or used, as detailed in our FAQ: https://wpml.org/faq/can-i-get-a-refund-for-automatic-translation-credits/.
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: WPML Support Forum.
Problem: You are experiencing an issue with the String Translation table on your site after installing WPML, which could potentially become a critical issue in the future. Solution: If your site is new and has no translated content, we recommend resetting WPML and setting it up again. Please follow these steps: 1. Ensure you back up your database and website. 2. Navigate to WPML >> Support >> Troubleshooting (the link is at the bottom of the support page). 3. Click on "Reset and deactivate WPML" then delete the plugin. 4. After deleting all WPML data and related plugins, reinstall the WPML plugins. For more detailed instructions, please visit: WPML Reset Documentation
If this solution does not resolve your issue or if it 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 the problem persists, please open a new support ticket at WPML Support Forum.
Problem: You are using Formidable Forms Lite with WPML on a site translated into 4 languages. When a user submits the contact form, the email notification is sent 4 times, with all emails arriving at the same timestamp and with identical content. This issue occurs because Formidable Forms notifications are being triggered once per WPML language. Solution: We recommend upgrading to Formidable Forms Pro and installing the Formidable WP Multilingual Add-On. This setup is necessary to properly manage multilingual forms and prevent duplicate notifications. You can find more details on setting this up in our documentation here: Translate sites built with Formidable Forms. If you prefer to explore other form plugins that are compatible with WPML, please check the list here: Compatible forms plugins.
Please note that this solution might be irrelevant if it's 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 at WPML support forum.
Problem: The client is experiencing an issue where footer translations in a multilingual WordPress site using WPML revert to the source language in the admin area after updates, despite displaying correctly on the front-end. Solution: 1. **Scan your theme for strings**: Ensure WPML has scanned the 'Bootstrap Basic New' theme for all translatable strings. * Go to WPML → Theme and plugins localization. * Under the Strings in the themes section, select your Bootstrap Basic New theme. * Click the Scan selected components for strings button.
2. **Check for your footer text in String Translation**: After scanning, search for your footer text. * Go to WPML → String Translation. * Search for a unique part of your footer text. * If found, ensure the translation is correctly entered and marked as Translation complete.
3. **If not found, check Admin Texts Translation**: Footer content might be in theme options, considered 'admin texts'. * On the WPML → String Translation page, scroll down and click the Admin Texts Translation link. * Look for your footer text under theme or customizer settings, select it, and click Add to String Translation. * Search again in String Translation, enter the translation, and mark it as Translation complete.
4. **Clear Caches**: Clear any caching plugins or server-level caching.
If these steps do not resolve the issue, or if the solution 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. If the problem persists, please open a new support ticket for personalized assistance at WPML support forum.
Problem: You are encountering a deadlock error when trying to get a lock in the context of the Dark Mode Switcher. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Click the small 'x' icon on the warning message to attempt to remove it. 2. Refresh the dashboard to see if the warning message still appears. If the message disappears, everything is likely in order. If the issue persists, it may require further investigation. For more detailed information, please refer to the following documentation: WPML documentation on dealing with error messages.
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: Der Kunde hat Probleme bei einem Custom Theme unter VErwendung von ACF, das beim Duplizieren eines Inhaltes von Deutsch nach Französisch entsteht. Die Bildergalerie wird nicht vollständig übernommen; entweder wird das Beitragsbild oder die Bildergalerie übertragen, aber niemals beides. Solution: 1. Installiere das Add-on "Advanced Custom Fields Multilingual", das unter Plugins > Plugin hinzufügen auf dem Reiter "Kommerziell" verfügbar ist. 2. Setze in jeder ACF-Feldgruppe die entsprechenden Übersetzungsoptionen. Verwende die Einstellung "Gleiche Felder in allen Sprachen verwenden" beim Übersetzen mit dem WPML-Übersetzungseditor. Für Übersetzungen mit dem WordPress-Editor oder beim Duplizieren von Inhalten verwende "Unterschiedliche Felder pro Sprache". 3. Synchronisiere die Medien unter WPML > Einstellungen > Media Translation > Manuell einrichten, nachdem die automatische Erkennung der Medien in dieser Sektion deaktiviert wurde.
Diese Lösung könnte veraltet sein oder nicht auf dein spezifisches Problem zutreffen. Wir empfehlen, die bekannten Probleme zu überprüfen, die Version des dauerhaften Fixes zu bestätigen und sicherzustellen, dass du die neuesten Versionen von Themes und Plugins installiert hast. Sollte das Problem weiterhin bestehen, öffne bitte ein neues Support-Ticket.
