Problem: The client is unable to display the Polish translation of the footer on their website, despite having renamed the Polish footer and being able to locate it via WPML translation management. The footer is integrated using the shortcode '[fl_builder_insert_layout slug="footer"]' in the Customizer.
Solution: We recommend the following steps to resolve the issue: 1. Ensure you have a full backup of your website. 2. Delete the Polish footer by navigating to Beaver Builder > Vorlagen, switching the language to Polish at the top-bar, and sending it to the trash. 3. Permanently remove the item from the trash. 4. Return to the German version of Vorlagen and click on the '+' sign to add a translation to Polish. 5. Name it 'Footer' and set the type to Footer. 6. Select 'copy content from German'. 7. Create the translation.
After following these steps, the footer should display correctly in Polish.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: You are trying to display individual elements with translation on the frontend of your site, but some elements, like a PowerPack Card Slider, are always displayed in German on the translated English page. Solution: First, ensure that the card slider content is available in the Advanced Translation Editor. Try making a small change to the page title or content, save it, and then update the translation to see if this resolves the issue. If the problem persists, the card slider content might not be registered for translation. We recommend you create a custom XML configuration code to register the card slider content for translation. You can follow our documentation here: How to Register Page Builder Widgets for Translation.
If this solution does not apply to your case, or if it seems outdated, please 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 contact us directly at the WPML support forum.
Problem: You are trying to exclude a single page from translation on your site, even though automatic translation is active. Solution: We recommend switching to the "Translate What You Choose" mode from WPML > Settings > Translation mode. This allows you to manually select which pages to translate automatically. For detailed steps on how to send pages for translation in this mode, please visit Translating Individual Pages, Posts, and Other Content Automatically.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client reported that the main navigation links in their header menu were not being translated into English. The website uses Beaver Builder, and despite attempts to retranslate the element and use the link target translation feature, the issue persisted. Solution: We resolved the issue by editing the translated template directly in Beaver Builder and translating the URLs. We recommend checking if the menu items now work as expected. If this solution does not apply to your case, or if it seems outdated, please visit our known issues page, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If the problem persists, we encourage you to open a new support ticket for further assistance at our support forum.
Problem: Sie haben Schwierigkeiten, die Links im Menü des Beaver Builders korrekt anzupassen, insbesondere werden nicht alle Links korrekt übersetzt, wie die Links auf der Startseite im Logo. Solution: Wir empfehlen Ihnen, das WordPress-Speichergrenze (WP Memory Limit) auf mindestens 256 MB zu erhöhen. Aktuell ist Ihr WP Memory Limit auf 40M gesetzt, während das PHP Memory Limit bei 1024M liegt. Um das WP Memory Limit zu erhöhen, verbinden Sie sich mit dem Server Ihrer Website und öffnen Sie die Datei wp-config.php in einem Text-Editor. Diese Datei befindet sich im Stammverzeichnis von WordPress. Fügen Sie folgenden Code kurz vor dem Kommentar
// That's all, stop editing! Happy blogging.
ein:
define('WP_MEMORY_LIMIT', '256M');
Nach dieser Änderung sollten Sie die Menüpunkte unter Design > Menus je Sprache korrekt anpassen können. Für dynamische Links, diese werden automatisch angepasst, sobald die Seiten übersetzt wurden. Weitere Informationen finden Sie hier: Übersetzen von Menüs. Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) 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.
Problem: The client reported that while the mega menu content was translated, the main menu items "Our competences", "About us", "Career", and "Become a partner" were not translated and linked to incorrect URLs. Solution: We successfully translated the menu items using standard WPML translation tools. The specific elements were set up in Beaver Builder under the row titled "Mega Menu Singhammer". For future reference, the client can apply the same WPML tools for translating other parts of their website.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: Sie haben Schwierigkeiten, die Links im Beaver Builder Menü auf Ihrer Website korrekt anzupassen, insbesondere werden die Links auf der Startseite im Logo nicht korrekt übersetzt. Lösung: Wir haben Ihre Anfrage in einem spezifischen Ticket weitergeleitet. Bitte folgen Sie diesem Link, um die Diskussion und die Lösungsvorschläge zu verfolgen: WPML Support Ticket.
Falls diese Lösung aufgrund von Aktualisierungen oder weil sie nicht auf Ihr spezifisches Problem zutrifft, irrelevant sein sollte, empfehlen wir Ihnen, ein neues Support-Ticket zu ö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: The client is trying to translate a custom post archive created with ACF from German to English, specifically from 'leistung' to 'service'. However, when attempting to edit the slug in the Archive Settings in ACF, it also changes the German slug. Solution: We recommend going to WPML > Settings > Taxonomies Translation and setting your custom taxonomy to "Translatable - only show translated items." Next, enable WPML > Settings > Slug translations and translate the slug accordingly. If this does 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.
