Problem: Sie haben einen Newsletter mit Fluent Forms erstellt und mit WPML übersetzt. Nach dem Löschen des Original-Newsletters ist die Übersetzung immer noch im Translation Management sichtbar. Solution: Dies ist ein erwartetes Verhalten. Das Translation Management von WPML listet alle Übersetzungs-Jobs auf, auch wenn das Original gelöscht wurde. Um die Übersetzung des gelöschten Newsletters zu entfernen, müssen Sie den entsprechenden Eintrag direkt in der Datenbank löschen. Eine Anleitung zu den betroffenen Tabellen finden Sie hier: https://wpml.org/errata/reducing-size-of-icl_translate_job-icl_translate-and-other-wpml-tables/ Bitte sichern Sie Ihre Datenbank, bevor Sie diese manuelle Bereinigung durchführen.
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.
Problem: You are trying to achieve alphabetical sorting of Buddyboss groups in different languages. The sorting works correctly in English, but when you switch to another language, it does not adjust to the translated names. The alphabetical sorting is based on English group names even when switched to another language, instead of sorting by the translated group names. Solution: We have escalated the issue to our developers, but currently, there is no workaround available as it likely requires major refactoring of the code. We recommend you follow the updates on this issue on our errata page.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues on 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 was unable to translate products using Elementor after installing the WPML plugin. Certain text within the Product Template was not appearing in the WPML translation editor.
Solution: 1. We advised the client to set the Woodmart Layouts to "Translatable" in WPML > Setting > Post Type Translation > Layouts (woodmart_layout) and then proceed to translate them. 2. For the untranslated string in the footer bar, it should be translated using WPML > String Translation. If the string is not visible there, the client should follow the guide to find and register the string for translation: finding strings that don't appear on the string translation page, and ensure the correct source language is set: how to change the source language of strings. 3. We recommended changing the WPML settings from "Translatable - use translation if available or fallback to default language" to "Translatable only show translated items" for both products and templates to ensure proper functionality. 4. We installed an update for the WooCommerce Multilingual addon to address compatibility issues, detailed here: WooCommerce Multilingual 5.5.0.
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 problems persist, please open a new support ticket.
Problem: The client is experiencing UI issues on their website pages when the WPML string translation plugin is enabled, specifically in the Indonesian language. Solution: We recommended enabling WP Debug to gather more detailed error logs. The steps include modifying the 'wp-config.php' file to enable WP_DEBUG, WP_DEBUG_LOG, and SCRIPT_DEBUG while disabling WP_DEBUG_DISPLAY. This setup helps in logging errors without displaying them on the site. For detailed instructions, visit WPML Debugging Documentation and WordPress Codex on Debugging. Additionally, to address potential issues with page updates not reflecting in translated versions, we suggested: 1. Open the default language page in Edit mode. 2. Make a minor change (e.g., add a space or + sign in the page title). 3. Save the page. 4. Remove the change made in step 2. 5. Update the page again. 6. Attempt to open the translated page in the WPML Translation Editor to check if it loads correctly. If these steps do not resolve the issue, we advised opening a new ticket for further investigation.
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 at WPML Support Forum for personalized assistance.
Problem: The client is experiencing issues with the UI of some Indonesian pages on their website not displaying correctly after translating the website into Spanish using the WPML String Translation plugin. Deactivating the plugin resolves the issue, suggesting a problem with string translation. Solution: 1. We recommended the client to provide debug information to better understand the site configuration. This can be done by following the steps at https://wpml.org/faq/provide-debug-information-faster-support/. 2. If the issue is related to menu translation: - Navigate to Appearance > Menus. - Select the problematic menu and switch to the translated language. - Delete the translated menu and synchronize it again by following the steps at https://wpml.org/documentation/getting-started-guide/translating-menus/. 3. Check if reducing the text size in the menu buttons resolves the issue, as oversized text might be causing layout problems.
Please note that the solution provided 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 at WPML support forum for further assistance.
Problema: Quando un cliente pubblica un Post o una Discussione nel forum, viene automaticamente creata una notifica nell'activity feed. Il cliente desidera che siano visibili solo le notifiche di una lingua selezionata. Nonostante il comportamento di default dovesse permettere il filtraggio delle notifiche per lingua, una regressione nella versione 2.8.80 di BuddyBoss Platform ha interrotto questa funzionalità. Tuttavia, il cliente utilizza una versione precedente di BuddyBoss, quindi teoricamente il filtraggio per lingua dovrebbe funzionare. Soluzione: Abbiamo confermato che si tratta di un bug noto. Abbiamo già contattato BuddyBoss per una soluzione definitiva. Poiché il fix deve essere implementato da BuddyBoss, consigliamo di aprire un ticket di supporto con loro, dato che le richieste dei clienti hanno spesso priorità maggiore.
Se questa soluzione si rivela irrilevante, perché potrebbe essere datata o non applicabile al tuo caso, ti invitiamo a verificare i problemi noti correlati, a controllare la versione del fix permanente e a confermare che hai installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti raccomandiamo di aprire un nuovo ticket di supporto con noi qui.
Problem: You are experiencing a 'Bad Gateway' error when trying to access a newly translated page from English to Spanish using WPML. Additionally, there are no new logs in the 'Advanced Translation Editor Error Logs'. Solution: We have tested the issue by deploying the site locally and found that the error does not occur in a local environment. This suggests that the problem is likely related to your server settings in the production environment. We recommend checking your server configuration or contacting your hosting provider to resolve this issue.
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 the issue persists, please open a new support ticket with us for further assistance.
Problem: If you're encountering a PHP Fatal Error when trying to access the WPML admin page, it might be due to a conflict with the Visual Composer PRO plugin, which registers a custom post type without proper labels. Solution: First, ensure you back up your database and website. We recommend trying one of the following workarounds: Workaround 1 (recommended): Add the following code to your theme’s functions.php file:
Workaround 2: Manually edit the plugin file at /wp-content/uploads/visualcomposer-assets/addons/themeEditor/themeEditor/PostTypeController.php. Replace the existing register_post_type function with:
protected function registerPostType()<br />{<br /> if (!isset($this->postNamePlural)){<br /> $this->postNamePlural = $this->postNameSlug;<br /> }<br /> register_post_type(<br />}
Note that this change might be lost if the plugin updates. We also recommend reporting this issue to the Visual Composer PRO team for a permanent fix.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.