You are experiencing a server 500 error when clicking the 'Mark Complete' button on translated LearnDash courses in French (Canadian). This issue might be related to the table structure of the course's lessons and topics in the translated version.
Solution:
First, ensure you are following the steps recommended in our documentation to translate LearnDash Courses, which must be done manually. You can find the guidelines here:
If the issue persists, please upgrade to the latest version of WPML (4.7 series) after a full site backup. Check for updates in the Plugins>>Add New>>Commercial tab.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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: The client was experiencing an issue where the URLs in the Nectar Slider were not being translated correctly and were always pointing back to the English version.
Solution: We provided a workaround to address the issue with the Nectar Slider post type. Before proceeding, we emphasized the importance of backing up the database and website.
3. Apply the same workaround for button 2 URL around line 845 with similar custom code. 4. After creating and translating a Nectar Slider post, edit a page, add the Nectar Slider element, select the slider location, save, and translate the page. The internal URL will then be adjusted in the frontend.
Please note that this solution might be outdated or not applicable to your case. If it doesn't resolve your issue, 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 you still need assistance, please open a new support ticket.
Problem: The client was trying to offer a translated version of a post but encountered an issue where the translated content was not displaying correctly, showing the default English content instead of the French translation. Solution: We resolved the issue by performing the following steps: 1. Edit the page in the default language. 2. Add "V2" to the title and update the page. 3. Delete the "V2" from the title and update the page again. 4. Update the translation. We recommend the client to check if the translated page is now working correctly. If this solution doesn't look relevant, we encourage the client to open a new support ticket.
Problem: The client wants to customize the language switcher in the main header menu to display shorter language codes (like EN) instead of the full language names, without modifying the full language naming list used elsewhere on the site.
Solution: 1. We recommend going to WPML > Languages > Site Languages > Edit languages and adding the custom language code for each language. For detailed instructions, please refer to our documentation: Editing WPML's Languages Table.
2. If you want to use a custom language switcher with different labels for each language, you can configure this by creating a custom language switcher and choosing which labels to display. For more information, please see our documentation: Custom Language Switcher.
3. To display a second language in the switcher only when a translation for a post/page is available, set the translation preference to "Translatable - only show translated items" in WPML > Settings > Post Types Translation.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
