The only reason why the 3.3.3 milestone was marked as completed is because leaving the milestone open interfered with our ticket reports for 3.4.1. (I forgot that milestone closures are reflected in the timeline.) Generally speaking, we assign tickets to the next minor milestone if they are reporting an immediate regression. So, a regression in … Read more
Try to make a new admin user in the db. Follow these steps you should be able to create a new admin user, then update and then you can give your old user admin rights again. Or use the new user. Your old user might have wrong setting in the DB http://www.dnawebagency.com/how-to-add-an-admin-user-to-the-wordpress-database
I for myself use a combination of: one file dedicated to the one-time script using a transient to stop the script from accidentally running more than once using capability-management or user-control to ensure the script is just run by me. Structure I use a file (onetime.php) in my include-folder inc, which is included in the … Read more
It is an automatic lock to prevent simultaneous core updates. It will be gone after 15 minutes. If you don’t want to wait, delete the record from options table – usually wp_options. Since WordPress 4.5: option_name=”core_updater.lock” If you have an older installation (before WordPress 4.5): option_name=”core_updater”