First things first
- Are you prompted for FTP credentials when you upgrade WordPress currently?
- How did you create the test install? Did you use SVN, or just download the beta zip file and extract it onto your server?
There’s been a bunch of changes too, so try manually updating, and see if it updates to the latest nightly, and then see if automatic updates kick in..
After seeing the issues you had with the Beta Tester plugin, I’d say your server doesn’t have OpenSSL installed or configured.
When WordPress cannot talk to WordPress.org over a secure channel (https) automatic updates are disabled, as it cannot verify that the package it’s going to install is legit.
One simple way to determine this, is to run a manual update, you’ll see it downloading the update from either “http://” or “https://”, if it’s the latter (https) then SSL works, if it’s just http, SSL isn’t able to work on your server, which is causing the issues.
Are you prompted for FTP credentials when you upgrade WordPress currently?
No, I don’t have provide my credentials.
How did you create the test install? Did you use SVN, or just download the beta zip file and extract it onto your server?
From a beta-zip file.
One simple way to determine this, is to run a manual update, you’ll see it downloading the update from either “http://” or “https://”, if it’s the latter (https) then SSL works, if it’s just http, SSL isn’t able to work on your server, which is causing the issues.
The manual update downloads the update over https/SSL.
There’s been a bunch of changes too, so try manually updating, and see if it updates to the latest nightly, and then see if automatic updates kick in..
I now manually updated to RC2, and will see if that fixes the problem. Is there a place where I can see when new builds come out?
Are you getting any emails from WP about this?
Do you have DISSALOW_FILE_MODS or any of the constants that kills it?
You SHOULD get an update at 7am and 7pm so check then, I guess.
