Problem: You have translated your website content using WPML, but when navigating from one page to another, the translation language reverts to the default.
Solution: If you're experiencing this issue, we recommend translating your menu to the target language properly. Since you are using 'Custom Links' in your menu, these links need to be manually updated in the translation to correspond with their translated URLs. We have provided a demonstration on how to fix this for a top-level menu item in French. Please check the related known issues at https://wpml.org/known-issues/ and ensure you have the latest versions of themes and plugins installed.
If this solution does not apply or is outdated, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to see the French content in the translated header and footer, although other parts of the website are translated. Solution: We reviewed the header and footer and found that the menus used in these sections had not been translated into French. We recommend translating the menus by following the steps outlined in this documentation: Translating Menus. Once the menus are translated, the header and footer should display the French content correctly.
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: You are using WordPress and Elementor for your website and have translated content for all pages. However, the translated content is not visible on the front-end, even after clearing cache and using incognito mode. Solution: 1. Go to the problematic page (e.g., Careers page) and edit it. 2. Make a slight change to the title, update the page, and then revert the change. This action can help trigger the page translation and update the translation status. 3. Access the WPML translation editor. You might find that some new fields have been added and some forms included in the translation. 4. Complete the translation for these new fields and forms. Note that if forms are involved, you will need to translate the forms in the editor, as only the English strings might be filled initially.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket.
Problem: The client needed to know how many translation credits are required for translating specific pages and custom post types, and whether credits are consumed when switching languages on the site. Solution: We advised the client to check the word count for the desired pages and post types by navigating to WPML → Translation Management and selecting the relevant items. To calculate the required translation credits, we recommended using the WPML automatic translation pricing calculator, which can be found here: Automatic Translation Pricing Calculator. Additionally, we clarified that translation credits are only used for creating new translations. Once content is translated, it does not incur any further charges when users switch between languages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. We also highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
