premise : I am not so sure as to the exact reason of your problem, but after the comments, and considering a normal “user” level of coding expertise, I post this answer describing not the ultimate solution, but the steps that I myself would have considered when facing a similar problem. There might be better … Read more
You say you included class-wp-upgrader.php, but the Codex page for request_filesystem_credentials() indicates that the function is defined in /wp-admin/includes/file.php. That’s the file you’d need to require() before you can use it. Looking at the source of class-wp-upgrader.php, the request_filesystem_credentials() function is part of the WP_Upgrader_Skin class, not a standalone function. There’s no guarantee that WP_Upgrader_Skin::request_filesystem_credentials() … Read more
I’m sure there is another way to fix it, but you could always try to do a fresh install. Make sure you backup your database and theme files, of course, and then just drop them into the new install. Not the most eloquent solution, but it has worked for me in the past when I … Read more
Log queries: You could collect all the queries during core/plugin/theme upgrades to see what happens. Just follow these two steps: 1) You should add: define( ‘SAVEQUERIES’, TRUE ); to your wp-config.php file to collect all queries during a page load into the $wpdb->queries array. Just remember to remove it afterwards. 2) Then you could log … Read more
To whom it may need. Here is the codes. I hope it helps someone. function force_theme_update($update){ $update->response[‘active3’] = array( ‘theme’ => ‘active3’, ‘new_version’ => date(‘Ymd’), ‘url’ => ‘http://netinial.com/theme/theme.php’, ‘package’ => ‘http://netinial.com/theme/theme.zip’, ); return $update; } if(current_user_can(‘manage_options’)){ add_filter(‘site_transient_update_themes’, ‘force_theme_update’); }
Eventually after confirming that the database had been updated I rebooted the server I tried moving the file wp-admin/upgrade.php to be wp-admin/411.upgrade.php. This got the site out of its death spiral. Given that I had manually updated all the files using Upgrading_WordPress_Extended and had also managed to get the database upgrade installer to run as … Read more
GitHub Plugins With Automatic Upgrades is a highly detailed article I’m referring to related to a project I have which will require automatic (one button) upgrades for both GitHub hosted + Website hosted plugins. The idea is very simple. During the upgrade process, your code modifies the WordPress internal data structures to look enough like … Read more
(Answering my own question) It is now 1 week after posting my question. I just revisited the dashboard. There are now two updates available: WordPress 4.3.1–nl_NL and WordPress 4.3.1–en_US. So it looks as if the localized update takes some more time to prepare. I will not click anything right now, assuming that the update will … Read more
It does seems that installation was customized in some way, either in regard to user account or user interface. If that is option at all I would politely inquire with last developer about customization performed. Beats digging through code. As for core update specifically — the “manual” way would be to delete old core files … Read more
You could just add a check for is_admin() and current_user_can(“update_plugins”) to make sure you’re running only for admin users that are currently in wp-admin. Any user browsing the front end won’t notice anything, logged in or not. You will probably also want to make sure that this runs only once to avoid race conditions that … Read more