Problem: The client is using a headless WordPress setup and is encountering issues when trying to access translated content via the REST API. The translated content is only returned when the client is logged in as an administrator; otherwise, the default language content is served. Solution: 1. We recommended the client to ensure that all translated pages are fully translated and published. 2. We advised checking if the second language is hidden in the WPML settings under WPML > Languages. 3. The correct approach to access translated content via the REST API is to include the language code before the REST API path. For example:
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.
Problem: The client has all strings translated for their theme, but they do not appear on the site unless 'Auto register strings for translation' is enabled. Solution: 1. We suggested that the client should try to delete the registered string, register it again, and then run the translation. 2. We noticed that all the client's posts were marked as needing an update. We updated the translation of a specific post to ensure it was completed to 100% and revised the posts. 3. We confirmed that the string "< Back to Main List" was correctly translated to "< Retour à la liste principale" after the update. 4. We also pointed out that the option "Look for strings while pages are rendered" was not enabled, which could be related to the issue. If the solution provided here does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 the problem persists, please do not hesitate to open a new support ticket with us.
