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
Is there any way to test if a function running only on plugin update is successfully running? Yes. Background When you update a plugin, WordPress does several actions behind the scenes. Download the new version of the plugin Deactivate the old plugin version Delete the old plugin version Extract the new version Activate the new … Read more
WordPress will check twice a day ( 12 hours ). This time can drift because WordPress doesn’t use traditional server cronjobs but cheap cronjobs which rely on user actions to trigger them such as viewing a page. So it could be 13 hours for when the updates are trigger but it still won’t run automatically, … Read more
So basically there a few more things to watch out when debugging this issues. I did the following and everything works like a charm. Downloaded the Background Update Tester plugin to see if there are any conflicts. Your WordPress install can communicate with WordPress.org securely. No version control systems were detected. (I had .git folder … Read more
The way WordPress uses to find a plugin in repository is not public AFAIK. As per Otto answer in question you linked it involves plugin url header alongside plugin name. BTW, remove the plugin from the list of plugin to update is the best way to ensure this problem is not going to happen again: … Read more
Every 12+ Hours WordPress automatically goes out and checks if a plugin needs to be updated via the WordPress Repository. There’s 3 cron jobs that WordPress runs to check on things: wp_version_check – Checks for Core Updates wp_update_plugins – Check for Plugin Updates wp_update_themes – Checks for Theme Updates A neat little plugin to view … Read more
Maybe the hook init is to late for the class and method go(), the update functions run earlier? The hooks muplugins_loaded and update_option start before the init. I have not test your code, is only a hint, not a solution. Maybe also helpfull a analyse of the hook order in the screenshot, create via plugin.
Yes it is. Though perhaps not in the way you might be thinking. If you check out some of the shared hosting sites, many of them have the capability to automatically update your WordPress site. Of course, as Milo has said, it can be rather disastrous too. Especially on a site with lots of plugins … Read more
I know this is kind of a backwards way of doing it, but I suppose if you disable the possibility to upgrade the plugin, then you don’t need to worry about the plugin being overwritten. Change the plugin version number (in the plugins main file comment header) to something ridiculously high so it won’t recommend … Read more
As far as I understand it is not related to specific permissions – Auto Update overall requires that files owner matches user Apache runs under. If that is not the case it falls back to other filesystem methods (FTP, SSH) and so prompts for password. You can define credentials in constants in wp-config.php so you … Read more