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: Exception
This topic contains 37 replies, has 2 voices.
Last updated by Prosenjit Barman 1 year, 9 months ago.
Assisted by: Prosenjit Barman.
Author | Posts |
---|---|
April 4, 2023 at 2:19 pm #13401131 | |
walter-arielM |
Hello there. Everything is updated now. You can proceed. |
April 5, 2023 at 10:37 am #13409089 | |
Prosenjit Barman Supporter
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hello There, Thanks for updating them. The 2nd tier team is currently inspecting the issue. I will surely let you know as soon as there is any information for you. I appreciate your patience and kind cooperation in this matter. Best Regards, |
April 7, 2023 at 4:28 am #13424787 | |
Prosenjit Barman Supporter
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hello There, I have received an update from the dev team. It seems the Flatsome theme is probably using some custom requests in its own page builder while saving the contents and maybe that is what causing the issue. It is suggested to not switch settings between the Translation editor and the native WordPress editor. As a workaround, please add the constant below in the wp-config.php file. define( 'WPML_TRANSLATION_AUTO_UPDATE_ENABLED', false ); You can find more information about this workaround here- https://wpml.org/errata/page-builders-translated-content-is-overwritten-with-the-original-when-updating-the-original-post/ I implemented the suggested changes on the staging site and everything seems to be working fine now. Kindly check this video(hidden link) for a better understanding. Let me know if that helps or if you need further assistance in this matter. Best Regards, |
April 7, 2023 at 10:13 am #13426425 | |
walter-arielM |
Hello Prosenjit, Well, I added and tried this line of code one week ago and did not work. I commented this to you in the second message of this ticket (take a look). Right now it seems to work fine. |
April 10, 2023 at 6:45 am #13436097 | |
Prosenjit Barman Supporter
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hello There, The dev team has suggested this workaround only. No other changes were made by them inside the code. However, It should be noted that I removed certain constants, such as Post Revision and Autosave Interval, from the "wp-config.php" file and added the new constant. I then conducted multiple tests to confirm that the issue is no longer occurring. So, if you want, you can make the same changes on your production site and then add the workaround. I hope you'll get the expected result on your production site as well. Let me know the update. We are always here to assist you. Best Regards, |
April 12, 2023 at 10:17 am #13454271 | |
walter-arielM |
Hello Prosenjit, Ok, thanks. I will check it today. |
April 13, 2023 at 11:27 am #13464035 | |
Prosenjit Barman Supporter
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hello Walter, This ticket will be kept open for up to 14 days. Then our system will close this thread. Please check by taking time and let me know the update. We will be glad to help you if you need further assistance in this matter. Best Regards, |
May 9, 2023 at 2:59 am #13609387 | |
Prosenjit Barman Supporter
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hello There, We haven't heard from you in a while, and we're assuming that the issue we were working on together has been resolved. If you still require our assistance, please let us know, and we'll be happy to help. In the meantime, if you have any further questions or concerns, please don't hesitate to reach out to us. We value your business and want to ensure that everything is satisfactory on your end. Looking forward to hearing from you. Best regards, |