Note that the github page tells us to download âswitch-to-classicpress.zipâ but that asset is not shown in the latest release. So I tried with the âsource codeâ zip link.
How long? A couple of minutes is normal when the server doesnât have a lot of bandwidth to download from other sites. Usually, though, the update will complete after at most 2 or 3 minutesâŚ
Are there any errors in your error log? Have you migrated any other sites with this server / hosting company?
Iâm trying to switch a localhost site on a computer thatâs doing nothing else, with a 16Mbps broadband connection. Iâve done it before successfully on two localhost sites though that was with the beta.
The page shows the downloading message while itâs still loading, and it stays in that state (partly loaded) for an average of two minutes, then the page finishes loading but without displaying any further messages. Itâs like it just gave up.
Thereâs nothing in my error log but my JavaScript console says Failed to load resource: net::ERR_INCOMPLETE_CHUNKED_ENCODING
Could it be the timeout settings on my Apache or PHP?
For some reason, after 10 failed tries yesterday, just now it worked (without making the changes in the PR cited above). The initial download part of the process took about 30 seconds.
FYI, my localhost server (XAMPP) is running cURL 7.45.0 with OpenSSL 1.0.2n.
I have a suspicion that my ISP might have been having problems yesterday and the connection to Github might just have been lost part way through each time.
One curious thing: on my dashboard page, the âAt a Glanceâ widget shows âClassicPress 1.0.0+migration.20190305 running RCG3 theme.â I would have expected it to just say â1.0.0â.
EDIT: after using the âIf you need to re-install version 1.0.0, you can do so hereâ option on the updates page, the at a glance widget changed to âClassicPress 1.0.0 running RCG3 theme.â
This is normal - the migration process uses slightly different builds of ClassicPress. The top-level folder of the build has to be called wordpress in order for the WordPress update system to process it, but our official release builds are not structured this way.