Problem: The client reported that their website's menu URLs do not stay in the translated language when navigating the site. Despite syncing the menus multiple times, all menu links default to the English version instead of the expected translated versions. Solution: 1. Verify that the correct pages/URLs are assigned for each language by editing the menu for the default language and checking the translated menus. Detailed steps can be found here: Translating Menus with Custom Links. 2. Ensure that the menu is not being loaded via a template (like an Elementor header template) that has not been translated into other languages. Also, verify that the correct menu is selected in the default language settings. 3. Translate the header template and update URLs in the WPML editor to ensure they work correctly across languages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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: Nach dem Importieren von Beiträgen mittels des WordPress Export-Tools (WXR) und der Verwendung von WPML Export und Import auf einer neuen Website, sind die Übersetzungen zwar den Sprachen richtig zugeordnet, jedoch nicht miteinander verbunden. Der Sprachumschalter erscheint nicht, und die WPML-Metabox zeigt "Übersetzung hinzufügen" anstatt einer Verbindung zu bestehenden Übersetzungen. Solution: Stellen Sie sicher, dass WPML Export & Import auf beiden Websites aktiviert ist. Vor dem Exportieren, gehen Sie zu WPML > Export & Import und folgen Sie den Anweisungen, um sicherzustellen, dass die notwendigen Sprachinformationen in der Exportdatei enthalten sind. Ohne diese Informationen kann WPML keine Verbindungen zwischen den Inhalten herstellen. Nach dem Import auf der neuen Website, wiederholen Sie den Vorgang unter WPML > Export & Import und schließen Sie die Migration ab. Für eine detaillierte Anleitung besuchen Sie WPML Export und Import Dokumentation.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, 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.
Problem: Sie haben Schwierigkeiten, ein Modul korrekt zu übersetzen, da bestimmte Teile des Moduls im Übersetzungsprozess nicht erscheinen. Solution: Wir empfehlen Ihnen, die folgende Konfiguration in Ihre WPML-Einstellungen einzufügen. Fügen Sie diese Custom XML Configuration unter WPML -> Settings -> Custom XML Configuration ein:
Dadurch sollte das Label im Translation Editor erscheinen. Wenn Sie weiterhin Probleme mit dem
desc_text="<p>EN Paketauswahl</p>
haben, könnte dies nicht direkt mit WPML zusammenhängen. In diesem Fall kontaktieren Sie bitte die Autoren des Plugins.
Sollte diese Lösung veraltet sein oder nicht auf Ihr Problem 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.
Problem: The client is experiencing an error 525 on a multilingual webpage after installing SSL. The content appears empty, and despite setting up SSL certificates for all subdomains, the error message 'Not valid' still appears. The client has configured A records for language subdomains on Cloudflare. Solution: We recommend checking if the domains are set up correctly by following the testing method in our documentation: Testing if the domains are set properly. This involves ensuring that each domain shows the website without redirection when WPML is deactivated. Additionally, ensure that each site translation has an SSL certificate, or use a multi-domain SSL certificate. You can also test if the website is redirected using tools like wheregoes.com. If issues persist, consult with a network specialist or your domain registrar to verify SSL and DNS settings.
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 further assistance is needed, please open a new support ticket with us.
Problem: After removing and reinstalling WPML plugins, an error appears indicating a problem with the String Translation table, which could become critical in the future. Solution: To fully reset WPML and avoid issues with leftover database tables, follow these steps: 1. Navigate to WPML → Support. 2. Click on Troubleshooting (link at the bottom of the page). 3. Scroll down and click on Reset WPML. 4. Confirm the reset to completely remove all WPML data, including translation tables. 5. Reactivate WPML plugins. 6. Run the setup wizard again. This process should resolve the String Translation table warning. Remember, this action is irreversible and will delete all existing translations, so ensure you have a backup if necessary. For more detailed instructions, visit WPML documentation on resetting the plugin.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client needs to know how many WPML translation credits they have used so far this year and in the past six months to estimate future needs and decide how many more to purchase. Solution: We provided the client with the current statistics for their site. To estimate the credits needed for future translations, we advised the client to go to WPML > Translation Dashboard and mark the content that needs to be translated. This action will generate an estimate of the required credits. Additionally, we informed the client that the cost per word varies depending on the selected translation engine, and we recommended checking the detailed pricing at https://wpml.org/documentation/automatic-translation/automatic-translation-pricing/.
If this solution does not fully address your issue, or if it seems outdated or irrelevant to your specific case, please do not hesitate to 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 visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: If you're experiencing issues where certain segments of your posts are not being translated when using automatic translation, despite using the default WP Gutenberg editor and trying different translation engines. Solution: We recommend checking if your server meets the minimum requirements for running WPML effectively. You can find these requirements here: https://wpml.org/home/minimum-requirements/ Firstly, contact your hosting support team to increase the PHP MEMORY LIMIT to at least 256M. Additionally, increase the WP MEMORY LIMIT in your WordPress installation to at least 256 MB by adding the following code to your wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');
Place this code just before the comment:
// That's all, stop editing! Happy blogging.
After adjusting these settings, ensure to back up your site and database. Then, update your plugins by going to Plugins > Add plugin > Commercial tab and clicking "Check for Updates". Once updated, edit the original content, save it, and attempt the translation again. If the problem persists, it might be due to other reasons, or the solution might be 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 these steps do not resolve the issue, please open a new support ticket with us for further assistance.
