Autosave happen in random page and posts

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	9:00 – 12:00	-
-	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	13:00 – 18:00	-

Supporter timezone: Asia/Singapore (GMT+08:00)

Tagged: Exception

This topic contains 37 replies, has 0 voices.

Last updated by Kor 11 hours, 58 minutes ago.

Assisted by: Kor.

Author	Posts
June 18, 2025 at 7:40 am #17144805
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your reply. You can exclude the media as it is not required to replicate the issue. You can probably share the entire site with an empty uploads folder.
June 19, 2025 at 6:34 am #17148695
davidP-136	Hi Kor, please enable private chat. I will share SFTP details. Do you still need a snapshot of the site, which you can do on your end, if required.
June 19, 2025 at 12:41 pm #17150670
davidP-136	Hi Kor, Any update?
June 19, 2025 at 3:04 pm #17151344
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your patience. I'm creating a snapshot now and will update you regarding the status.
June 19, 2025 at 4:05 pm #17151714
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your patience. I have a copy of the site now, and I will escalate this to our 2nd Tier Support and will come back to you as soon as I have feedback.
June 24, 2025 at 5:02 am #17162929
davidP-136	Hi Kor, did you find anything? how much time it will take?
June 24, 2025 at 7:32 am #17163250
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your reply. I’ve received some initial feedback from our 2nd Tier Support, but they needed further clarification. I’ve followed up with them and am now waiting for their response.
June 24, 2025 at 5:18 pm #17166288
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your patience. I've a feedback from our 2nd Tier Support and this is what he mentioned. I just did a little testing on my local test site with WPML plugins disabled and I employed the Jetpack code to disable autosave via dequeuing the script and I found it doesn't seem to work, there were still autosaves added to the database. So, I would strongly recommend to use the "traditional" way of "disabling" autosave by setting the interval very high. For example. Insert this custom PHP code into your wp-config.php file. define('AUTOSAVE_INTERVAL', 86400); Then check without WPML to clarify that it has the intended effect, and then check with WPML to confirm it continues to work as intended.
June 25, 2025 at 6:49 am #17167223
davidP-136	Hi Kor, We have already implemented this on both the live and the provided staging environments: hidden link Additionally, we’ve dequeued the autosave script using an MU plugin: hidden link The autosave has stopped for new pages as expected. However, as mentioned in the shared ticket, the issue still persists on the existing pages. I had already highlighted this in the initial ticket. Let me know if you need any further details.
June 25, 2025 at 7:47 am #17167396
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your reply. I've shared your feedback, and I will come back to you once I hear from them.
June 26, 2025 at 8:22 am #17171918
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Thanks for your patience. I've some feedback, and this is what our 2nd Tier Support mentioned. As I found previously, there is no autosaving going on when autosave has been "disabled" via setting a very long interval, regardless of whether WPML is active or not. I suspect the problem on the client site may be related to leftover autosaves in the database from before they tried to disable them, and having dequeued the autosave script, perhaps that prevents the leftovers from being tidied up. I suggest the client delete the leftover autosaves from the database and disable further autosaves just by setting a long interval (remove dequeuing the autosave script, it's a core script and could possibly have unintended consequences). As we advance, I wouldn't expect them to encounter any autosaves amid the post revisions. They can use a simple query to remove the leftover autosave: DELETE FROM wp_posts WHERE post_name LIKE '%autosave%' AND post_type LIKE 'revision' Let us know how it goes.
June 26, 2025 at 12:43 pm #17173547
davidP-136	Hi Kor, let me check
June 26, 2025 at 1:45 pm #17173977
Kor WPML Supporter since 08/2022 Languages: English (English ) Timezone: Asia/Singapore (GMT+08:00)	Ok, let me know how it goes.
June 26, 2025 at 2:13 pm #17174072
davidP-136	Hi Kor, Something strange is happening. I deleted the autosave entries for the following: Page: hidden link Post: hidden link Now, when I edit the page and leave it idle for about 30 seconds, then refresh the page, the autosave appears once — but if I refresh it again, the autosave disappears. Sometimes it creates an autosave, and sometimes it doesn’t. This same behaviour occurred on the new duplicate page we shared with you on the first comment of this ticket: hidden link Is there a known root cause for this? If we delete autosaves, does that resolve the issue permanently, or will the same issue return when duplicating a page or its content?
June 26, 2025 at 2:36 pm #17174276
davidP-136	Hi Kor, Also, we have removed dequeued the autosave script which is added in mu plugins.