Matt

Thank you Guust! Cheers.

I was referring to the errors Guust found earlier, I’ve asked about them several times in this thread with no answer, this is the first time I’ve been told they’ve been resolved and don’t appear anymore. Thank you.

Hi Kiran, since Guust found JSON cache errors on my site, could you please take a look and see if there are any problems I need to address regarding this?

Hi Kiran, I’m not seeing the popup warning about unsaved changes like before, that’s a definite improvement.

Regarding the message on the edit page – “Hey, we found some unsaved changes…” – the first time I went to your test page I did not see it. But returning to the page a second time brought back the message, and it has stayed there even after clearing cache. I can click to dismiss it and save the page, and the next time visiting it won’t be there, but leaving and coming back to the page will trigger it again, even with no changes made.

That’s where I think it could be confusing for the user if that message is presented regardless of whether any changes were made. The user is being told “Hey, we found some unsaved changes from earlier and are showing them below.” But there are no changes to find, and the user is left looking for supposed changes that don’t exist. This will happen every time they visit the edit page and don’t make a change.

The message then says “If you would prefer to start again then please click here to remove this revision.” A user may think “I don’t want to start all over. So I better not click it.” They can leave the page without clicking that message but it’ll be there when they return. If they click it and save the page, it’ll be gone temporarily but will return in subsequent page visits, even if no changes are made.

It all seems unnecessarily complicated. Why not only present that message if actual unsaved changes exist?

Also,

1. Regarding the “minor changes for autosave execution” that you made – is this a setting or adjustment that I can make on my other sites?

2. If I decide to turn off autosave, I have the snippet below. Do you forsee any problems or conflicts using it?

add_action( 'admin_init', 'disable_autosave' );
function disable_autosave() {
        wp_deregister_script( 'autosave' );
}

3. What do you think is the reason for older autosaves suddenly showing up on the main edit pages? Guust mentioned some JSON errors related to caching, is that something that can be fixed?

Thanks!

Hey Kiran, that was an issue with the host’s firewall and I’m told it’s been resolved now.

Hey Kiran, I just used those FTP credentials to set up a new connection with Cyberduck and successfully connected. Not sure why you’re unable to – anything else I can try on my end?