Problem: You are trying to ensure that the translated pages on your site use the same template as the English version after installing WPML. However, the translated pages do not use the same template as the English ones, and you are unable to change the template for them. Solution: The issue is likely related to how Elementor templates and WPML translations are linked. Here’s how you can ensure your translated pages use the same (or a translated) template: 1. Go to Templates → Theme Builder in your WordPress dashboard while in the default (English) language. 2. Locate the template used for your English pages. Ensure it’s assigned with the proper Display Conditions. 3. Switch to your secondary language using the language switcher in the top admin bar. 4. Go back to Templates → Theme Builder and click Add New to create a template for the secondary language. Design it as needed, then publish it, but do not set Display Conditions for this template. 5. Switch back to the default language, return to Templates, and edit your original (English) template. 6. In the right sidebar, find the Language box and click Connect with translations. Select or search for the new template you just created in the secondary language and assign it. If you’re unable to change the template for translated pages, it’s usually because the templates aren’t linked across languages, or Display Conditions are set incorrectly for the secondary language template. Ensure only the default language template has Display Conditions set.
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 the problem persists, please open a new support ticket.
Problem: Sie möchten den Sprachumschalter im Header Ihrer Website anpassen, um die Sprachen nur mit Flaggen nebeneinander anzuzeigen, statt in einem Pulldown-Menü. Solution: Wir empfehlen Ihnen, die Einstellungen im Flatsome Theme zu überprüfen, da es sich nicht um eine Funktion des WPML-Sprachumschalters handelt, der ein spezifisches Markup verwendet. Sie können verschiedene Optionen für die Anzeige des Sprachumschalters in Abhängigkeit von Ihrem Theme und Ihren persönlichen Präferenzen finden. Weitere Informationen und Anleitungen zur Einrichtung finden Sie hier: WPML-Dokumentation zum Hinzufügen von Sprachumschaltern.
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: The client is using a multisite installation dedicated to WooCommerce and encountered an issue with the String Translation table, which could potentially become critical in the future. Solution: We suggested that the client first try translating a string on their site to check if the String Translation table is functioning correctly. If the problem persists, we recommended cloning the site to another staging environment for further troubleshooting.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with translated 'account' pages showing as blank and Elementor templates and JetFormBuilder forms not displaying in French on their website. Solution: 1. Ensure that JetEngine Profile Builder pages are set as Translatable in WPML → Settings under the Post Types Translation section. 2. Verify that each account page has a French translation by checking under the French flag in Pages. Edit and update the French version if necessary. 3. If the navigation menu is missing or blank in French, go to Appearance → Menus, select the French menu, and ensure all relevant profile/account pages are added and published in French. 4. Use WPML → String Translation to translate any static or dynamic text, such as menu labels or JetEngine-generated elements. 5. Set Elementor templates and JetFormBuilder forms to Translatable under Post Types Translation in WPML → Settings. Check for French translations in Templates → Saved Templates and JetFormBuilder → Forms, and add or review the translation as needed. 6. Use the Advanced Translation Editor to verify and publish the translation. 7. Clear any site or browser cache if the preview still does not show the template in French. 8. If issues persist, consider switching to the parent theme temporarily to rule out issues with child theme customizations.
If after following these steps the issues persist, or if you encounter any error messages or blank content, it might be necessary to consult further with our support team. 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 the problem continues, please open a new support ticket at WPML support forum for personalized assistance.
Problem: The client is experiencing an issue where ACF fields in the hero layout become readonly on a translated page, despite being set to 'Copy Once'.
Solution: 1. Verify that the ACF field and its sub-fields within the Flexible Content field are set to 'Copy Once' in WPML → Settings → Custom Fields Translation. 2. Ensure you are using the WordPress Editor to translate the page. If using the WPML Translation Editor, switch to the WordPress Editor by clicking the pencil icon next to the translation and selecting the WordPress Editor. 3. After switching, check if the hero layout ACF fields are editable on the translated page. If they remain readonly, review the field group settings in ACF → Field Groups to confirm correct translation preferences. 4. If issues persist after these steps, remove the translation and recreate it using the WordPress Editor to correctly apply the 'Copy Once' setting.
If the solution provided does not resolve your issue or seems outdated, we recommend opening a new support ticket for personalized assistance. Additionally, please check related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and confirm the version of the permanent fix. For further support, visit our support forum at https://wpml.org/forums/forum/english-support/.
