Problem: Der Kunde hat Probleme mit der Anzeige von BuddyBoss Profiltypen in einer viersprachigen Multisite-Seite. Die Profiltypen erscheinen teilweise mit leeren Feldern oder in allen Sprachen, obwohl sie übersetzt wurden. Dies führt zu weiteren Problemen bei der Auswahl des Typs für WordPress- und LMS-Rollen. Solution: Wir empfehlen, einen bereits bekannten Workaround in einer Staging-Umgebung zu testen, um das Risiko von Fehlern auf der Live-Site zu minimieren. Der Workaround ist in unserer Errata-Seite beschrieben: https://wpml.org/errata/buddyboss-translating-profile-types/. Es ist wichtig, dass die Tests nicht direkt in der Live-Umgebung durchgeführt werden. Ein permanenter Fix ist in der Entwicklung und wird in der zukünftigen Version von "BuddyPress Multilingual 1.8.0" erwartet, allerdings steht das genaue Datum noch nicht fest.
Falls diese Lösung veraltet erscheint oder nicht auf Ihr Problem zutrifft, empfehlen wir, die neuesten Versionen Ihrer Themes und Plugins zu überprüfen und bei weiteren Fragen ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu besuchen: https://wpml.org/known-issues/. Für weitere Unterstützung können Sie sich gerne an unser Support-Forum wenden: https://wpml.org/forums/forum/deutsch/.
Problem: Der Kunde konnte die Strings von Germanized Pro nicht übersetzen, insbesondere die Checkboxen im Checkout-Prozess. Dies lag daran, dass WooCommerce über Blocks und nicht über Shortcodes verwendet wurde, was möglicherweise zu Kompatibilitätsproblemen mit Germanized führte. Solution: Zuerst empfahlen wir, den Germanized Support zu kontaktieren, um zu überprüfen, ob es ein Problem mit der Kompatibilität gibt. Zusätzlich haben wir eine benutzerdefinierte XML-Konfiguration in WPML > Einstellungen > Benutzerdefinierte XML Konfiguration hinzugefügt, um die Strings für die Übersetzung zu registrieren:
Anschließend haben wir den Kunden angewiesen, die Ausgangssprache der Strings anzupassen und deren Übersetzung zu testen. Weitere Informationen zur Anpassung der Ausgangssprache finden Sie hier: Wie man die Ausgangssprache von Strings ändert.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) 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. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support-Forum.
Problem: You are experiencing a 404 error on the homepage of your site when it is set to the English language. Solution: First, check if there is an /en folder where WordPress is installed. Next, navigate to WPML->Languages->Language URL format and switch to 'language as a parameter' URL format to see if the English page appears correctly. Additionally, we recommend trying the workaround detailed in this documentation: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/.
If these steps do not resolve the issue, it might be because the solution is 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 at WPML support forum for further assistance.
Problem: You are experiencing errors after updating WPML and WPML String Translation, including 'open_basedir restriction in effect' warnings and 'Cannot modify header information - headers already sent'. The system attempts to access an incorrect path, leading to these issues. Solution: We recommend checking the specific errata page related to this issue on the WPML site. Please visit https://wpml.org/errata/php-warning-file_exists-open_basedir-restriction-in-effect-warning-possible-with-current-string-translation/ for a detailed explanation and potential fixes.
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 with us for further assistance.
Problem: The client was experiencing an issue with Gravity Forms Multilingual version 1.8.0 and above, where the 'gform_review_page' filter did not display the review page as expected, only showing the submit button directly.
Solution: We recommended trying the solution from this erratum.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with translating ACF repeater fields registered via PHP using the WPML editor, where the field doesn't translate correctly and only shows the number of rows instead of the array, this might be similar to your situation. Solution: We recommend trying the workaround mentioned in the WPML errata for issues related to the translation preference of PHP registered system fields. You can find more details and steps on how to apply this workaround at Advanced Custom Fields local fields translation preference issue for PHP registered system fields.
If this solution does not resolve your issue, or if it 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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
You are trying to update translations in a secondary language using WPML, but after translating, the gear icon still appears instead of the pencil icon. You are wondering why the gear icon appears after translating and how to ensure the pencil icon appears after translation.
If this solution does not resolve your 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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to complete the translation of your forms using WPML, but you are encountering an issue with Font Awesome glyph icons in HTML. Strings with glyph icons are not saved, and the translation is not 100% completed, leaving some English text on translated pages/forms. Solution: 1. Increase the PHP memory limit to at least 512M. You can do this by adding the following code to your
wp-config.php
file just above the line that says '/* That's all, stop editing! Happy blogging. */':
2. Enable the previous version of the Advanced translation editor. Go to the advanced translation editor, click the gear icon on the top right to access settings, enable the 'Previous version' option, provide feedback, and submit to reload the page. 3. Apply the fix for a known issue with Gravity Forms by following the steps outlined here: https://wpml.org/errata/gravity-forms-merge-tags-are-available-for-translation/
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 at WPML support forum.
The client is experiencing issues with inaccurate translations in a multilingual donation form, particularly in Chinese (Simplified and Traditional). The form supports English, Chinese, and French, but the translations for Chinese are not functioning correctly except for a few fields.
Solution:
We have identified that it is not possible to translate Give Donations forms like normal posts and pages using the WPML Translation Editor due to a compatibility issue. The Give WP team is also aware of this. To address this, you should:
1) Ensure you have the latest versions of WPML, Elementor, and Give WP installed. 2) Create a separate donation form for each language, specifically for Chinese Simplified or Traditional. 3) Test the new form by creating a simple page in the desired Chinese language and adding the form using the shortcode:
If this solution does not resolve your 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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: Hai creato un template popup con Elementor per il menu del sito e lo hai tradotto con WPML. Il popup si apre correttamente in italiano, ma nelle altre lingue, si apre sempre in italiano nonostante l'header sia nella lingua corretta. Solution: Il problema che stai riscontrando potrebbe essere legato a un bug noto con Elementor e i popup tradotti. Ti consigliamo di seguire il workaround disponibile in questa pagina: https://wpml.org/errata/elementor-translated-popups-not-displaying-correctly-in-page-builder-container-links/.
Se la soluzione proposta non risolve il problema o se le informazioni risultano obsolete, ti invitiamo a verificare la versione della correzione permanente e a confermare che hai installato le ultime versioni dei temi e dei plugin. Inoltre, ti consigliamo di consultare la pagina dei problemi noti di WPML qui: https://wpml.org/known-issues/. Se il problema persiste, non esitare a aprire un nuovo ticket di supporto nel nostro forum di supporto WPML.
