V4.1.4.1 – Auto-Save Issue with Facebook data

Hey @hiskingdomprophecy,

Thank you for reporting this.

I tried reproducing this issue, but I couldn’t. I’ll ask one of my colleagues to try as well, but since we didn’t make any significant changes to the metabox in the latest update, this is probably happening due to a conflict with another plugin.

I’d recommend temporarily disabling those other two plugins and see if that resolves the issue. If you’re able to trace it down to one particular plugin, let us know and we’ll take a look and see if we can resolve the conflict.

If you’d rather have our support team take a look, feel free to reach out to us here via our Basic Question form – https://aioseo.com/contact

@arnaudbroes

Thank you for your prompt reply.

I have done a full check using Health Check and AIOSEO V4.1.4.1 conflicts with Classic Editor 1.6.2

As soon as I turn on the Classic Editor and refresh a post, all the AIOSEO data is lost.

I am not using blocks at all on my site. It is all old school.

Please kindly have a look, as I cannot disable my editor.

If I can help you further, please let me know.

Regards and thanks,
Angus

@hiskingdomprophecy as far as we know (and I had a colleague double-check this), auto-saving our data in the Classic Editor has never worked. This is because the Classic Editor sends an internal AJAX request to save their data and our plugin saves on regular POST requests. We also checked a few other plugins that register metaboxes and their data isn’t saved either during an auto-save. We also tried this with older versions of both AIOSEO and the Classic Editor plugin.

The only way you are able to save our data is through the “Update” button that sends a regular POST request and then refreshes the page. We can look into adding support for this possibly but it shouldn’t have worked in the past.

@arnaudbroes

Thank you.

Perhaps I have my wordings wrong previously.

I will let you know what I do and what the result is.

I start a new post, add a title, add content text, add an extract, insert a featured image from the library, then under AIOSEO I add in a URL for a custom Facebook image.

I then save draft using the “Save Draft” button. As the page refreshes, all the above contents is there. All works as previously.

However, if I click the “Save Draft” button again, the page will refresh without the AOISEO Facebook images. It is deleted.

Not only is the Facebook image missing, but the selection of “Custom Image” – which open the box below for the url, is not there. It is as if I have not ever entered anything into the AIOSEO Social tab. All is gone.

If I add the custom url back again and save draft, it stays until I save draft again…. which will delete it.

However, with Classic Editor off, all works normally.

I just rolled back to 4.1.3.3 and all works perfectly. “Save Draft” does not remove AIOSEO data and I can save draft as often as I want.

After updating again to 4.1.4.1, the second time I hit “Save Draft” all AIOSEO is removed from the post.

When I initial reported this I was in a mental production mode, not test mode, and I thought that the WP autosave was causing the issue between saves – which may be a long time. That was wrong. The issue is that a second “Save Draft” command on Classic Editor removed my AIOSEO data, which is not and was not the case on 4.1.3.3.

I hope this helps you understand the issue.

To save me production frustration, I have rolled back to 4.1.3.3 pending a fix.

If you need more help, like a HAR, please let me know.

Regards and thanks,
Angus

Hey @hiskingdomprophecy,

Thank you for the detailed write-up. I’ve now been able to reproduce this and have confirmed it’s a bug. I already have a fix in the works so we’ll probably issue a hotfix for this today.

@arnaudbroes

Thank you for letting me know, and thanks in advance to you and your colleagues for the fix.

Regards and thanks,
Angus

@hiskingdomprophecy just wanted to let you know we’re going to release tomorrow instead just so that we have enough time to properly test the update. ??