Problem: The client is experiencing compatibility issues with the 'Monogram – Personal Portfolio WordPress Theme' which claims to be '1000% compatible with WPML.' The client needs to know if the theme has been officially tested, certified, or approved by WPML, and if there are any known issues related to this theme. Solution: We confirmed that the 'Monogram – Personal Portfolio WordPress Theme' has not been tested or officially certified as compatible with WPML. This does not necessarily mean that the theme will not work with WPML, but it indicates that the theme's compatibility is managed by the theme authors. We recommend that the theme authors apply to our official compatibility program through our Go Global program to ensure full compatibility. If you're experiencing specific translation issues, please provide more details so we can assist further. It's possible that a particular setting may have been overlooked.
Please note that this solution might be 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 issue persists, please open a new support ticket.
Problem: WPML indicates that pages are translated, but most of the content remains in the default German language, despite being viewed in other languages. Solution: The issue arises because the theme's custom Elementor widgets are not registered for translation. To resolve this, follow these steps: 1. Ensure the WPML Multilingual Tools add-on plugin is installed and active. 2. Edit a page in the ORIGINAL language (German) that is not displaying translations. 3. Scroll to the section titled "WPML: Elementor Widgets". 4. Copy the XML content under the subtitle "XML generated for widgets from this page that does not have translation settings.". 5. Paste this XML into WPML -> Settings -> Custom XML Configuration. Ensure it's placed in the correct section, typically for shortcodes. 6. Update the settings, then make a minor edit to the original page/post. When you edit the translation again, the previously missing content should now be visible.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm 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: The client is experiencing issues with displaying the WPML language switcher in a custom header space created with Elementor and the Saasive theme. Solution: 1. Edit Your Header Template with Elementor: Access your WordPress admin, navigate to Templates → Theme Builder, and edit your header with Elementor. 2. Add the WPML Language Switcher Widget: In the Elementor editor, search for the WPML Language Switcher widget and add it to your header. 3. Customize and Publish: Customize the appearance of the language switcher and publish the changes. 4. Translate the Header: Ensure the header template is translated for all languages using WPML’s Translation Dashboard. 5. If the issue persists, consider adding the language switcher to the main menu for better visibility across all devices. You can manage this in WPML -> Languages -> Menu language switcher. 6. Adjust the style of the language switcher using CSS at WPML -> Languages -> Language switcher options -> Additional CSS.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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 WPML support forum.
Problem: The client reported that Google only indexes the English pages of their multilingual site, even when manually indexing other languages. The '/EN/' slug appears despite other languages being set up, and WPML is configured correctly.
Solution: We recommended the following steps to address the issue: 1. Ensure the WPML SEO Add-on is active by checking under Plugins → Installed Plugins. If not present, install and activate it from Plugins → Add New → Commercial tab. 2. Verify the presence and correctness of 'hreflang' tags on translated pages by viewing the page source and searching for 'hreflang'. 3. Check the WPML's Language URL format under WPML → Languages and ensure 'Different languages in directories' is selected. 4. Disable the Browser Language Redirect temporarily under WPML → Languages to avoid confusion during indexing. 5. Re-save permalinks under Settings → Permalinks and re-submit sitemaps in Google Search Console.
Additionally, we advised against using the Browser Language Redirect feature as it does not distinguish between users and search engine bots, which can affect SEO and indexing. This is documented in our guides:
If these steps do not resolve the issue or if the information seems outdated, we highly recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: The client is experiencing issues with the visibility of Footer Style 2 and difficulties in translating menus manually in different languages. Solution: 1. We have ensured that the header, footer, and contact form on the homepage are translated. We recommend the client to double-check these elements to confirm their translation. 2. To translate menus, follow the steps in our quick guide on translating menus. It's important to note that the translation seen in secondary languages might be related to the page titles included in the menu, not the menu items themselves. 3. To edit translated menus, navigate to Appearance -> Menus, select a menu, and click on the pencil icon to edit the menus in their corresponding language. 4. You do not need to create and translate the menus manually for each language. Menus can be automatically translated using the synchronization option, but manual edits can be made if specific adjustments are needed.
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.
Problem: If you're experiencing issues where the original colors of elements are replaced with different colors after translating your website using WPML, this might be due to the theme's custom elements not being registered correctly for translation. Solution: We recommend adding the following CSS code in the Appearance -> Additional CSS section to fix the color of the specific element:
Additionally, to prevent this issue in the future, ensure that the theme authors register their custom elements for translation by following the steps described in our documentation: Registering Custom Elementor Widgets for Translation.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: When switching to English, all texts remain in German, and the header is not visible. Solution: If you're experiencing issues with texts not translating and headers disappearing when switching languages, it's likely due to unregistered Elementor widgets. We recommend registering your custom Elementor widgets for translation. You can learn how to do this by following our guide on registering page builder widgets.
We have registered the elements in your header and footer, and they should now appear correctly translated. If you encounter untranslated content on other posts or pages, you should contact the theme authors to ensure they register the custom elements they created. You can refer them to the same guide.
Additionally, you can add the necessary XML code for registration in WPML -> Settings -> Custom XML Configuration tab as outlined in the guide.
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 problems persist, please open a new support ticket.
Problem: The client reported issues with incorrect translations in the menu across all languages and problems with the placement and visibility of the language switcher, especially on mobile devices. Additionally, the flags added to the menu were causing the header to shift, and there were discrepancies in media visibility across different languages. Solution: 1) We corrected the menu translations. The client needs to manually edit the translated menus to include translations for specific strings like 'About Us'. 2) For the language switcher issues, we recommended checking the guide on language switchers to learn about adding them in different locations. 3) To address the footer not being translated, the client should navigate to Footer-> All Footers in their site's admin area and translate the footer. 4) For media not appearing correctly in other languages, we advised going to WPML-> Media Translation and referred the client to the media translation guide.
If this solution does not resolve your issues or seems outdated, we highly recommend checking related 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.
