olgaD-8

Problem:
The client wanted to deactivate translations temporarily to import properties in English without incurring additional translation costs. They were unsure if they should deactivate the WPML plugin or if there was another method.
Solution:
We advised the client against deactivating the WPML plugin as it could lead to confusion with unfiltered translations appearing on the site. Instead, we recommended changing the translation settings in WPML to 'Translate what you choose' from 'Translate everything automatically'. This adjustment can be made in WPML > Settings. This way, the client can control what gets translated and avoid unnecessary costs. Additionally, we provided a link to hide languages from the front end if needed: https://wpml.org/documentation/getting-started-guide/language-setup/hiding-languages-on-the-front-end/

If this solution does not apply to your situation, or if it seems 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. Should you need further assistance, please open a new support ticket at WPML support forum.

Problem:
If you're experiencing an issue where the loading wheel keeps spinning indefinitely when trying to delete a language translation in WPML, it often indicates a problem with the website's backend processes.

Solution:
1. Increase Execution Time: The script might be timing out. Increase the PHP maximum execution time in your website's settings. This can often be done in the .htaccess file, php.ini file, or directly in WordPress if your hosting allows it.

2. Check for JavaScript Errors: Use your browser's developer tools (usually accessible by pressing F12) to check the console for JavaScript errors. If there are errors, they might point to the cause of the issue.

3. Inspect Network Activity: In the same developer tools, you can also monitor network activity to see if a specific request is failing. Look for any requests that do not complete or return an error.

4. Disable Caching Plugins: If you're using any caching plugins on your WordPress site, temporarily disable them as they can sometimes interfere with backend operations.

5. Server Resources: If your hosting server is under-resourced or experiencing high usage, it might not be able to complete the process. Check your hosting environment to ensure it has enough resources.

6. Deactivate non-WPML plugins for now: Please create a full website backup, then disable all the non-WPML plugins (leave just the WPML plugins active) and see if the issue is still happening.

If you have already opened another support ticket for the same issue, please continue the conversation there to avoid duplicate tickets. If this solution doesn't look relevant or if you need further assistance, please open a new support ticket.