Problem: Translators were removed from WPML and could not be re-added, although they still existed as accounts on the website. Solution: We found that the issue was caused by a corrupt key in the database. We removed the
wpml-cache-translators-translate
entry from the
wp_options
table in the database, which resolved the problem and the translator users were visible again in WPML.
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 the problem persists, please open a new support ticket.
Problem: You are trying to translate internal links from Swedish to English using WPML, but encounter issues where the links are not automatically translated and are not visible for manual update in the WPML editor. Solution: We recommend following these steps to address the issue: 1. Refer to our guide on translating links: https://wpml.org/faq/how-to-translate-links/ 2. If the links still do not appear in the WPML editor, try this: a. Open the page in the Advanced Translation Editor. b. Click on Settings and enable the option to show all links. c. Make a small change to the original page and save it, then revert the change. This action should trigger an update in the translation editor. d. Return to the translation editor to see if the changes are now visible.
If these steps do not resolve your issue, or if the solution 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. Additionally, feel free to open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing issues with WPML on a single Custom Post Type (CPT) page built with Elementor, where the translated page does not maintain the same slug across all languages. Instead of having a consistent slug like '/salesforce' for each language, it changes to '/salesforce-dk' and similar variations for other languages. Solution: We recommend the following steps to address the issue: 1. Ensure that you have a backup of your website. It's safer to perform these steps on a staging version of your site to avoid disruptions. 2. Update WPML and its add-ons by navigating to 'WordPress Dashboard > Plugins > Add new > Commercial (tab)', then click the 'Check for Updates' button. For more information, visit WPML automated updates documentation. 3. Go to 'WPML > Settings > Post Type Translation', find the post type in question, and ensure the slug translation matches the original. 4. Navigate to 'WordPress Dashboard > Settings > Permalinks' and click the 'Save' button to flush the permalinks cache. 5. If using separate domains for different languages, validate each domain under 'WPML > Languages' and ensure they point directly to the website without redirection. For more details, visit WPML different domains per language documentation.
If these steps do not resolve the issue or if the solution 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 the problem persists, please open a new support ticket for further assistance at WPML support forum.
