restricted access to wp-admin

BulletProof Security has my wp-admin locked down pretty tight, and I have never had any problem doing a WordPress upgrade.

@leejosepho: thanx for your answer. That is a good indication.

I was just wondering if there is anything that might go wrong, for instance during a database update (as part of the WP auto-update). Is there someone who is familiar with what is going on in the core files who can tell for sure if there is a problem (or not) with a wp-admin directory that has restricted access. I’d like to be sure before I auto-update…

Will there be a problem with the auto-update when access to the wp-admin directory is restricted through the use of a .htaccess file?

Background updates are only performed if PHP can update the files directly, so any .htaccess restrictions shouldn’t make a difference.

I was just wondering if there is anything that might go wrong, for instance during a database update (as part of the WP auto-update).

Background updates in 3.7 only deal with files, database update is a separate process. Database schema is not changed in minor releases.

@sergey:

Thanks for your answer. I guess my question partly came from a screenshot somewhere, where I saw a log entry in the auto-update e-mail mentioning the database update. That matches my experience where I see the database update mentioned on the screen with any automatic update in version 3.6 and less.

I guess it is only mentioned, but no changes are actually performed on the database.

That is rather confusing. I really don’t want to find myself in a situation where the source code is changed and a database update did not go thru.

I’ll try to trust that all changes are fine. If anything comes up along the way, I’ll know where to go.

Database updates in major releases are done with backwards compatibility in mind, so if the files are updated and the database is not (yet), the site should still work fine.