I have just made a plugin that needed to be autosaved, so i started to dig into the code. I did now that it have to be trigged by some javascript so started to look into the console in Chrome when autosave fires. I then saw that autosave.js looks for a class tags-input in admin-filters.php … Read more
Do it like shown below, as suggested by @gyo and done by @Howdy_McGee in his answer. function admin_queue( $hook ) { global $post; if ( $hook == ‘post-new.php’ || $hook == ‘post.php’ ) { if ( ‘targeted-posttype’ === $post->post_type ) { wp_enqueue_script( ‘custom-title-here’, bloginfo( ‘template_directory’ ) . ‘/scripts/custom-script.js’, ‘jquery’, ”, true ); } } } … Read more
CPU usage: AJAX and Heartbeat API on admin pages
It all depends on your workflow. If you have no use for the post revisions and autosaves then disable them in wp-config and WordPress will clean them up on its own. You may also prefer to limit how many you keep at once. Also the space they take up is unlikely to be of a … Read more
Autosave: Autosave is simply about saving your posts automatically in the background while you are editing. So it’s different from revisions and for every post there will be only one autosave per user. This is from the document: There is only ever a maximum of one autosave per user for any given post. New autosaves … Read more
So I found the solution, callback function for when post or page is: jQuery(document).on(‘heartbeat-tick.autosave’, function( event, data ) { // your code here }); This uses the WordPress Heartbeat API.
This should be placed in your wp-config.php (and no where else): define( ‘AUTOSAVE_INTERVAL’, 60*60*60*24*365 ); // Set autosave interval to 1x per year define( ‘EMPTY_TRASH_DAYS’, 0 ); // Empty trash now: Zero days define( ‘WP_POST_REVISIONS’, false ); // Do not save andy revisions