Problem: You are trying to ensure that your 'PAGE : Documentation' template is fully translated using WPML. Despite translating 100% of the fields, the WPML translations queue page still marks the template as 'In progress'. Solution: The issue arises due to the page builder logic for Elementor, specifically related to flushing the cache. This process overloads the memory and can cause a fatal error. A workaround involves modifying the code in the file:
Before applying this workaround, ensure you have a full website backup. 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 further assistance is needed, please open a new support ticket at WPML support forum.
The client is experiencing issues with ACF field group labels still appearing in WPML > Translation Management despite using the define('ACFML_EXCLUDE_FIELD_GROUP_STRINGS_IN_POST_JOBS', true); setting.
Solution:
The constant *ACFML_EXCLUDE_FIELD_GROUP_STRINGS_IN_POST_JOBS* just prevents new occurrences of ACF Field Groups listing for translation in WPML Translation Management Dashboard.
So we recommend adding the following code to your functions.php file, ensuring you take a full backup before making changes:
/**
* Exclude the ACF field group section on the Translation Management Dashboard.
*
* @see https://onthegosystems.myjetbrains.com/youtrack/issue/acfml-990
*/
add_filter( 'wpml_tm_dashboard_item_sections', function( $sections ) {
/** @var \WPML\UserInterface\Web\Core\Component\Dashboard\Application\ViewModel\ItemSection[] $sections */
return array_filter(
$sections,
function( $section ) {
return $section->getId() !== 'stringPackage/acf-field-group' && $section->getId() !== 'stringPackage/acf-options-page-labels';
}
);
} );
If this solution does not apply to your case, or if it becomes 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to reactivate German product translations on their WooCommerce site after changing domains. They encounter issues where WPML generates a placeholder product titled 'koppie' instead of linking the original products to their German versions. These translations remain either unpublished, missing, or incorrectly connected. Solution: We recommend the following steps to resolve the issue: 1. Visit the product/post/page on the front end and click to edit it. 2. On the sidebar, click to send the translation to the trash. 3. Visit the trash can in the secondary language (you can choose this on the top bar). 4. Completely delete the translation by removing it from the trash can. 5. Recreate the translation. This process should resolve any residual problems with the translations. If you find a translation still showing the issue, please delete and add it again. Ensure you always have a website backup before making these changes.
Please note that this solution might be irrelevant if it's 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 for further assistance.
Problem: If you're experiencing issues where WPML deletes image files from the server, particularly large images that WordPress scales (creating a file with a -scaled suffix), here's what might be happening. This issue occurs when you upload a large image (over 2560px) to the default language, and either delete the image from a secondary language or remove a language from the settings screen, which also removes leftover content. This results in the deletion of generated media files from the server, breaking the media library in the default language. Solution: We recommend updating to WPML version 4.7.2 or later, as this issue has been addressed in these later versions. If you're still facing this problem after updating, it might be due to other factors. In such cases, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.
If the solution provided here does not resolve your issue or seems irrelevant, we highly recommend opening a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client was experiencing issues with translated page lists returning empty and missing menus in the translated navigation. The expected submenu and page list were not appearing, and instead, there was an absence of these elements. Solution: We identified two separate issues. For the navigation menu problem, we found that the pages were not correctly added as parent/child in the Pages section. After adding them and re-translating the templates via WPML > Translation Management, the navigation displayed correctly. For the page list block inside a content template, it was determined to be a bug. The temporary workaround involved manually adjusting the translated IDs in the database for the wp_navigation and editing the page via Gutenberg in "Code" view to specify the translated "ref" value. We also recommended checking and translating these from WPML > Translation Management and manually selecting the correct translated parent page. A permanent fix was scheduled for WPML 4.8.
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 at WPML support forum.
Problem: Der Klient hatte zwei Hauptprobleme auf seiner Webseite. Erstens funktionierten die Links nicht mehr, weil die Kategoriebezeichnungen von Deutsch auf Englisch geändert wurden und er die Basis der Permalink-Einstellungen nicht auf Deutsch zurücksetzen konnte. Zweitens war das Einstellen neuer Produkte in mehreren Sprachen komplizierter geworden, wobei am Ende des Prozesses eine Fehlermeldung erschien. Solution: Wir haben eine Kopie der Website zur Analyse an unsere Entwickler gesendet. Nach der Untersuchung stellte sich heraus, dass ein seltener Fehler vorlag, der durch die Konfiguration der Kategorien und URL-Einstellungen verursacht wurde. Wir haben eine Korrektur vorgenommen, und die Probleme sollten nun behoben sein. Wir bitten den Klienten zu bestätigen, ob nun alles korrekt funktioniert.
Falls diese Lösung veraltet erscheint oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen unter 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 unter https://wpml.org/de/forums/forum/deutsch-support/.
Problem: Sie haben zwei Probleme mit WPML: Das Kopieren von Inhalten von Deutsch auf Englisch funktioniert nicht mehr wie früher, und es gibt 404-Fehler bei der Auswahl bestimmter Kategorien auf der englischen Seite. Solution: Wenn Sie ähnliche Probleme erleben, empfehlen wir Ihnen, folgende Schritte zu befolgen: 1. Erstellen Sie ein vollständiges Backup Ihrer Website. 2. Deaktivieren Sie alle Plugins, AUSSER: WooCommerce, WooCommerce Multilingual & Multicurrency, WPML Multilingual CMS und WPML String Translation. 3. Nehmen Sie eine kleine Änderung am Produkt in der Originalsprache vor und speichern Sie diese. 4. Öffnen, vervollständigen und speichern Sie die Übersetzung. 5. Wiederholen Sie die Schritte 3 und 4 für alle betroffenen Produkte. 6. Aktivieren Sie Ihre Plugins wieder.
Diese Lösung könnte veraltet sein oder nicht auf Ihr Problem zutreffen. Wir empfehlen Ihnen, 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. Wenn das Problem weiterhin besteht, öffnen Sie bitte ein neues Support-Ticket.