WordPress Autosave & Meta Slider Save Conflict

Hello,

I love your plugin, bought it with a paypal account that I have since closed and can’t locate the transaction ID at the moment (Hence the post here).

My issue has to do with your saving function.

background: In many cases, both for myself and clients (and others having similar issues accross the web based on my research), the wordpress “autosave” function has issues with, but not limited to, custom post types and revisions. The symptoms are that when autosaving a draft, the save and publish buttons become inactive, and the “autosave” never completes, therefore making it impossible to save the post without disabling the css that disables the buttons.

Because of this I use the following snippet in my child themes functions.php file to disable the autosave completely:

function theme_dequeue_script() {
  wp_dequeue_script('autosave');
}
add_action( 'admin_enqueue_scripts', 'theme_dequeue_script', 100 );

This results in a much more intuitive saving of drafts and publishing of posts both for myself and for my clients.

This however has an adverse effect on your plugin (assuming this is the conflict). The symptoms are that your settings never return from their save, much as the posts do when wordpress’ autosave is active. The data saves, and I am able to use all functions fine. Waiting 5 seconds then re-navigating to that screen confirms settings save, and all sliders work on front end as expected. The Preview however does not work, as it is tied to the end of the save (that never happens) I’m assuming.

MY QUESTION:
Do you think it would be better to dequeue the scripts on all admin screens EXCEPT your plugin? (if this is the case, what is your suggestion for properly targeting your plugins admin screens?)

——–

Sorry if this is long, wanted to be thorough! ??
Again, amazing work.

https://www.ads-software.com/plugins/ml-slider/