JSON parse Error on wp-json/wpml/tm/v1

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was unable to access the auto translation tools due to an error on "/wp-json/wpml/tm/v1". The issue persisted even with only WPML active and default themes. The client identified the issue within an output buffer and invalid HTML markup and fixed it.

Solution:
We recommended the following steps to troubleshoot the issue:
1. Verify that the server meets the WPML minimum requirements.
2. Create a full website backup.
3. Disable all plugins except for WPML and its add-ons.
4. Check if the issue still occurs.
5. If the issue is resolved, reactivate plugins one by one to identify the conflicting plugin.
6. If the issue persists with non-WPML plugins disabled, switch to a default theme like TwentySeventeen and test again.
We also suggested performing these steps in a staging environment if possible.

If these steps do not resolve the issue or if the solution provided here is outdated or not applicable to your case, we highly recommend checking the 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 continues, please open a new support ticket with us.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: ATE

This topic contains 2 replies, has 2 voices.

Last updated by oliverS-59 1 year, 1 month ago.

Assisted by: Mihai Apetrei.

Author	Posts
March 25, 2024 at 11:55 am #15446394
oliverS-59	i cannot access the auto translation tools due to an error on "/wp-json/wpml/tm/v1". If i check the source code, i find closing tags which causes the error. I dont have those tags on my other sites which are working well. This also happens with only WPML active and default themes.
March 25, 2024 at 12:01 pm #15446457
Mihai Apetrei WPML Supporter since 03/2018 Languages: English (English ) Timezone: Europe/Bucharest (GMT+03:00)	Hi there. Before this ticket gets assigned to one of my colleagues, I will try to help. This issue looks to me like it could be either caused by server-related causes or a compatibility issue between WPML and (at least) one of the active plugins or the active theme. 1. Please make sure that your server follows the WPML minimum requirements and that you are using the very latest WPML versions: https://wpml.org/home/minimum-requirements 2. If the issue is still happening, can you please let me know if it still happens even when only the WPML plugins are active and you are using a default WordPress theme? Please try the following steps so that we can test for a compatibility-related issue: - create a full website backup - disable all plugins except WPML and its add-ons - check if the issue is happening again - if it's not, reactivate your plugins one by one, checking every time if the issue shows up again so that you can understand which plugin is causing that issue If the issue happens even with the non-WPML plugins disabled: - leave all the non-WPML plugins deactivated - switch to a default theme like TwentySeventeen - try to recreate the issue now If you have the chance, it would be best to do this in a staging (testing) environment. Please let us know how that goes and if following any of these steps solved your issue or brought any change. We will be waiting for your response. Mihai Apetrei
March 25, 2024 at 12:16 pm #15446525
oliverS-59	Hi, i already wrote in my opening post: The issue still exists with default theme and only WPML active. Extra info: We have other wordpress instances running (which are clones) on the same server with exact same server settings, themes and plugins. The only differences are other languages and other language codes.
March 25, 2024 at 1:32 pm #15447096
oliverS-59	I found the issue within an output buffer and invalid html markup and fixed it.