This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is experiencing issues after migrating translations from Loco Translate to WPML. Some Hebrew strings were incorrectly marked as English in WPML, and the client wishes to revert to the original Loco Translate settings and then restart the translation process manually, ensuring accuracy.
Solution:
First, ensure that your site meets the minimum requirements for running WPML by increasing the WP Memory limit to 256M. You can do this by adding the following code to your
wp-config.php
file:
define('WP_MEMORY_LIMIT', '256M');
Place it just before:
/* That's all, stop editing! Happy blogging. */
After updating the memory limit, verify the settings under WPML > Support > WordPress and attempt to save the translations again. Ensure that the strings in WPML > String Translation are assigned to the correct source language by following the instructions here: How to Change the Source Language of Strings.
If you decide to revert to LocoTranslate, disabling WPML should return your site to its previous state. However, using the WPML reset feature is only recommended if you plan to stop using WPML entirely.
If this solution does not resolve your issue or seems outdated, please check for related known issues at WPML Known Issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket at WPML Support Forum.
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.
This topic contains 1 reply, has 2 voices.
Last updated by 7 months, 1 week ago.
Assisted by: Andreas W..