Problem: The client needed editors to access more WPML features, specifically the glossary function, without elevating them to Translation Managers. Despite being registered as translators, editors were unable to access or modify the glossary. Solution: We clarified that by default, editors do not have access to all WPML features. To allow editors to translate content, they must be added as translators via WPML->Translation Dashboard->Manage Translators & Services, which the client had already done. This setup enables editors to translate assigned content or initiate translations directly from pages or posts. However, for editors to access and manage the glossary, they must be assigned as Translation Managers. This role will allow them to update, add, or remove glossary items. The glossary itself automatically applies during translations in the Advanced Translation Editor, providing accuracy and context without direct editor intervention. For more details on managing glossary entries, visit How to Create and Manage Glossary Entries.
If this solution does not resolve your issue or seems outdated, we 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: The client is experiencing issues with receiving translations on the ACF Options Page when using GraphQL. They attempted to select a preferred language using GraphQL queries but were unsuccessful. Solution: We recommend using our official WPML addon for GraphQL, which can be found here: WPML GraphQL. Currently, it is not possible to use GraphQL with ACF Options Pages. We have noted this as a feature request for a future version and have added the client's vote to it.
If this solution does not resolve your issue or seems outdated, please check the 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. If the problem persists, we highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client is concerned about translating synonyms from Yoast SEO Premium in WPML's Advanced Translation Editor for better SEO across different languages. Solution: We clarified that the synonyms entered in Yoast's custom fields are used internally for calculating SEO scores and do not appear on the site or influence search engine indexing directly. Therefore, translating these synonyms in WPML will not affect your SEO as they are not visible to search engines. For effective multilingual SEO, focus on translating the main content and key phrases for each language, rather than the synonyms.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Also, check the related known issues, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: Editor users assigned as Translators are unable to translate content they previously could and receive the message "You can only edit translations assigned to you." This issue arose after recent WPML updates, and attempts to delete Translation Jobs to dissociate translations from any user were unsuccessful. Solution: To resolve this, follow these steps: 1. Edit the file
3. Ensure that the "Manage Options" capability is granted to the relevant users. Note: This change might allow editors to see more admin items. To limit visibility in the admin area, consider using a role/capability plugin like Advanced Access Manager. Be aware that any modifications made directly in WPML plugin files will be overwritten with future updates, so these changes will need to be reapplied after each update. Currently, these changes cannot be implemented via a snippet or hook, and there is no estimated time for when this functionality might be officially supported by WPML.
If this solution does not apply to your case, or if it becomes outdated, 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.
