Problem: The client was experiencing issues with a new WPML SEO plugin that was breaking their site upon activation. They were also curious about why they now need to link menu items, a step that was not necessary before, possibly due to a WPML update. Solution: If you're experiencing similar issues with a new WPML plugin affecting your site, we recommend deactivating the plugin temporarily and testing it on a staging site, as the client did. This approach helps isolate the problem, potentially linked to PHP and SSL configurations, which the client resolved separately. For concerns about linking menu items that previously worked without linking, this might be due to recent updates in WPML. We suggest reviewing the change logs of recent WPML updates to understand any changes in functionality.
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 for further assistance.
Problem: The client is using the Avada theme and has a separate French menu from the English one on their site. The main French menu is not displaying correctly, showing only the last tab while the submenus remain visible. Solution: 1. We recommended checking the menu settings in WordPress under WP > Appearance > Menu to ensure the correct menu is selected for the French version. 2. It's important to link the primary language "main menu" to its translated version as shown in the provided screenshot. This step is crucial for the menus to display correctly across different languages. 3. If issues persist, it might be due to synchronization problems which can occur if other methods of menu translation are used. We suggest reviewing the methods listed on Translating Menus to ensure proper setup.
If this solution does not resolve your issue or seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and consider opening a new support ticket for further assistance.
Problem: The client is unsure about the importance and functionality of the 'translate link targets' option in WPML. Solution: If you're experiencing confusion regarding the 'translate link targets' in WPML, it's important to understand that this feature is designed to help manage internal links in your multilingual site. When you insert internal links in a page or post, WPML automatically recognizes these as internal links and, if a translation is available, WPML will adjust the link to point to the translated version of the linked page. This feature is generally a troubleshooting tool and does not need to be used regularly unless you notice that some internal links are not being translated correctly.
Please note that this solution might be irrelevant if it's 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 for further assistance.
Problem: The client is seeing a notification about new translatable content but is unsure if they need to update the MO files regularly since they do not receive notifications to do so. Solution: We explained that the notification indicates the availability of new translatable content. It is not mandatory to update these MO files, especially if the strings are already translated as desired. We recommended that in the future, if the client cannot find a specific string, they should consider scanning the plugins and/or theme to find it. However, this is not necessary at the current moment.
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: The client is experiencing issues with global element updates not being imported correctly, such as background colors, and has questions about the 'post types translation' settings for global styles in the Avada theme. They are also concerned about notifications for updates to strings. Solution: We recommend ensuring that the settings are consistent across all languages. If the settings are set differently for each language, WPML will maintain these differences. To synchronize the settings, you can import your settings from one language to another, such as from EN to FR. This process will overwrite all old options with the imported settings. For detailed steps on how to import theme options from one language to another, please visit https://wpml.org/documentation/theme-compatibility/using-wpml-with-the-avada-theme/how-to-set-theme-options-for-languages-in-avada/#how-to-import-theme-options-from-one-language-to-another. Moving forward, we suggest changing the settings for 'All Languages' to avoid similar issues.
If this solution does not resolve your issue or seems irrelevant due to being 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are having trouble translating a section with nested tags, and attempts to redo the translation after deleting the original have led to site crashes and errors. Solution: First, ensure that your original content's nested tags are correctly formatted. Check that each tag is properly opened and closed in the right order. For example, the correct format should look like
<strong><em>...</em></strong>
, and not
<strong><em>...</em></strong>
. Once you've confirmed the tags are set up correctly, proceed with these steps: 1. Open the translation editor. 2. Delete the existing translation for the problematic segment. 3. Use the option to copy the original content into the translation editor to ensure all tags are correctly copied. 4. Translate the text within the tags without altering or removing the tags themselves.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current situation, we recommend opening a new support ticket. Additionally, please check the related known issues and ensure you have the latest versions of themes and plugins installed. For further assistance, you can also visit our support forum.
Problem: The client needs to set up a staging site for their website and is unsure whether to register it before pushing it live. They are also concerned about the registration of the staging site with WPML and the use of licenses. Solution: We recommend creating the staging site separately and using a new WPML key set as "dev" instead of "production". After setting up the staging site, install and activate WPML, then register it with the new key. For migrating the site to production, use the Duplicator plugin. This tool helps in migrating your website while maintaining the setup and updating URLs if needed. Documentation and a tutorial for Duplicator can be found at:
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
