Problem: The client's editor cannot edit content in the English language, although they can edit the default language (German).
Solution: We recommend checking if the editor is assigned as a translator for the English language by going to WPML > Translation Management > Translators. Here, you can define the language pairs for the user. For more information, please refer to this documentation: How to Set Up Local Translators and Language Pairs.
Another potential issue could be that the content is in the translation basket, which holds content pending translation. If necessary, clear the basket and attempt to edit again. For guidance on this, see: Translating Your Contents.
We suggest using the manual translation option as the best approach for your situation. If this solution does not resolve your issue, please open a new support ticket with us.
Problem: 1) A client created a new WordPress user with the editor role, but the user cannot edit content in languages other than the default language (DE). 2) The client wants to know if it's possible to edit content using the WordPress editor instead of the WPML translation editor. 3) The client inquires about the process of changing the WPML license from a dev site to a production site with a different domain.
Solution: 1) To allow the editor to edit content in other languages, you need to ensure that the user has the necessary language permissions. Check the WPML language management settings and assign the appropriate permissions to the user. 2) To use the WordPress editor for translations instead of the WPML translation editors, you can select the manual translation option. Each user who needs to translate content should follow the steps outlined in the documentation. 3) When you're ready to move your site from development to production on a different domain, update the WPML license accordingly. There are no additional steps mentioned for this process.
Problem: 1. The client has created a new WordPress user with the editor role, but the user cannot edit content in the English language. 2. The client wants to know if it's possible to edit content directly in the WordPress editor without using the WPML translation editor. 3. The client is inquiring about the process of changing the domain for their WPML-registered site when moving from a development to a production environment. Solution: 1. For the issue with the editor role, we recommend checking the user's permissions and ensuring that they have the necessary capabilities to edit content in all languages. If the problem persists, please open a new support ticket for further assistance. 2. To edit content directly in the WordPress editor without using the WPML translation editor, you can disable the WPML translation editor. For more information on how to do this, please refer to our documentation: Using Different Translation Editors for Different Pages. 3. When changing the domain of your WPML-registered site, you need to generate a new key for the new domain. Here are the steps: - After migrating the site to the new domain (using a migration plugin like Duplicator), - Visit https://wpml.org/account/sites/, - Remove the old key, - Generate a new WPML key for the new domain, - Copy the key, - Go to your newly-migrated website, - Navigate to Plugins > Add New > Commercial, - Register WPML with the new key. If this solution doesn't look relevant, please open a new support ticket at our support forum.
Problem: The client is experiencing fatal errors like
Uncaught TypeError: Illegal offset type in isset or empty in /wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-element-translation.php:259
on their English version pages after enabling media translation and clicking 'start' for the media translation in WPML.
Solution: 1. We identified that the issue might be related to the Advanced Custom Fields (ACF) plugin, where the theme is calling for an ACF field that contains the ID of an image, which WPML tries to translate. 2. We suggested disabling any caching plugins and server-related cache as a first step to resolve the issue.
Problem: ACF fields that have been deleted are still visible in the backend.
Solution: This is an ACF issue where deleted fields are not removed from the database, causing WPML to still display them. For a detailed explanation, refer to this post.
