Since version 3.7 WordPress has automatic background updates. By default, only minor releases – such as for maintenance and security purposes – and translation file updates are enabled on most sites. In special cases, plugins and themes may be updated. Of course, as with many things in WP, you can modify that behavior with config … Read more
Found a fix. Simply add the following snippet to functions.php for your theme: if(is_admin()) { add_filter(‘filesystem_method’, create_function(‘$a’, ‘return “direct”;’ )); define( ‘FS_CHMOD_DIR’, 0751 ); }
The first argument is the plug-in’s ‘slug’. The plug-in slug is determined by the location of the .php file header containing the comment header necessary for plug-ins. (see source). If your main plug-in file might be ~/wp-content/plugins/foo/bar.php, while your plug-in slug is foo/bar.php. If the wp-content dir has a custom name, you can retrieve it … Read more
I found the answer here: If the install uses FTP for updates (and prompts for credentials), automatic updates are disabled. (I found this answer which will tell you how to avoid using FTP.) If the install is running as a SVN or GIT checkout, automatic updates are disabled If the constants DISALLOW_FILE_MODS or AUTOMATIC_UPDATER_DISABLED are … Read more
There’s the site_status_tests filter, to e.g. remove the asynchronous background updates tests: add_filter( ‘site_status_tests’, function ( $tests ) { unset( $tests[‘async’][‘background_updates’] ); return $tests; } ); But one could argue that this is just hiding information from the user. Ticket #46733 suggests instead e.g. “…ignored tests section, hidden away like the Passed tests“, so the … Read more
Adding this filter in a must-use plugin or functions.php will allow automatic updates even if the site is under version control: add_filter( ‘automatic_updates_is_vcs_checkout’, ‘__return_false’, 1 ); From https://developer.wordpress.org/reference/hooks/automatic_updates_is_vcs_checkout/
A website is just like any other software product, any change need to go through QA stage first, no matter how trivial it might seem. This is why you should always test all updates on a staging/dev server before pushing it to production. As always it comes down to a question of ROI. Simple blogs … Read more
You’ll want to make a new ticket here: http://core.trac.wordpress.org/ Explain why you want a new hook and how it could be used. Including a patch file also goes a long ways towards getting the hook included in WordPress.
It’s quite possible. I’ve been doing this for years with my Version Checker plugin. I do not distribute it openly, but in essence it checks a private version API , and then tosses the extra results into the update_core, update_plugins and update_themes site transients. WP then takes it seamlessly from there courtesy of the WP … Read more
Do you need the “View Details” link? It shouldn’t show up unless it’s a WP hosted plugin. Could you just name the plugin whatever you want, but change it with JS in the admin function my_enqueue($hook) { if ( ‘plugins.php’ != $hook ) { return; } wp_enqueue_script( ‘my_custom_script’, plugin_dir_url( __FILE__ ) . ‘changeName.js’, array( ‘jquery’ … Read more