Problem: The client encountered a critical error when trying to create a root page using the 'Use directory for default language' option in WPML. The error was related to the translation_priority taxonomy and a specific post with ID 38470. Solution: We recommended a minimal setup test to identify the issue: 1. Temporarily switch to the Twenty Twenty-Five theme. 2. Deactivate any object cache like Redis or Memcached. 3. Keep only WPML Multilingual CMS and WPML String Translation active. 4. Attempt to recreate the root page. If successful, gradually re-enable the theme and plugins to pinpoint the conflict. Additionally, use WPML's Troubleshooting Tools by navigating to WPML → Support → Troubleshooting and running the following: - Set language information - Remove ghost entries from the translation tables - Fix element_type collation Finally, go to Settings → Permalinks and click Save. It's crucial to make a full site backup before proceeding with these steps, especially if the site is live. Consider performing these actions in a staging environment.
If the problem persists or the solution seems outdated, please 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. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing issues with the translation page not loading after adding custom languages, and encountering errors related to languages mapped to English, this might be due to a known issue in our code. Solution: We recommend implementing a temporary workaround until the permanent fix is available in WPML 4.8. You can find the workaround details here: Custom Database Prefix and Having 30+ Languages Can Cause a Database Error When Visiting Translation Dashboard.
This issue may arise particularly if you are using a custom prefix for your database tables, similar to our local environment setup.
Please try this solution and let us know how it goes. If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You want to rename built-in language names in the WPML language switcher dropdown, such as changing 'Norwegian Bokmål' to 'Norwegian (no)' and 'Portuguese, Brazil' to 'Brazil (Pt)'. However, you encounter issues because there is no option to edit a language once added, and attempting to add a custom language with an existing language code results in an error. Solution: To change the default language names for the language switcher, follow these steps: 1. Activate the pre-configured language you want to rename by going to WPML → Languages. 2. Change its locale by editing the language and assigning it a new locale (e.g., en_EN or a custom value). 3. Save the changes. 4. Now, add your custom language using the now-free original locale. For more detailed instructions on adding custom languages, visit Adding Custom Languages.
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 contact us at WPML support forum.
