Support » Fixing WordPress » Updating takes me to 4.2-alpha

  • Andre

    (@andrejcarter)


    When 4.1 RC1 was announced I used the beta tester plugin to update and it took me to 4.1 alpha. As suggested in https://wordpress.org/support/topic/i-now-have-42-alpha-1 I manually installed 4.1RC1 over the files to fix the problem. I also deactivated the beta tester plugin.

    Later it showed there was an update to core so I ran it via the built in updater and it took me back to 4.2 alpha. This was done with the beta tester plugin deactivated.

    Any explanation for what’s causing this?

Viewing 4 replies - 1 through 4 (of 4 total)
  • I have the same probleme.

    Moderator Jan Dembowski

    (@jdembowski)

    Brute Squad and Volunteer Moderator

    Off topic for a moment:

    @luciole135 You are not having the same problem: you said you have not installed any plugins on your localhost installation. If you don’t want to start your own topic that’s fine and your choice. But please do not pile onto other people’s topic when you say you do not have the same problem.

    Back to our regular scheduled support topic:

    When 4.1 RC1 was announced I used the beta tester plugin

    @andrejcarter Thank you for testing and that’s exactly what many people including myself did. Especially since that’s what the post says to try. 😉

    But when you set the plugin to use nightlies (also what I did) your installation pulled the nightlies build. Right now that’s set to WordPress 4.2-alpha and that’s why you’re now on that release.

    I (and many people I am sure) had the same exact experience. The way I solved it was to deactivate that beta tester plugin and manually install the WordPress 4.1 RC1.

    https://wordpress.org/wordpress-4.1-RC1.zip

    Once you’ve done that done and you’ve got 4.1 RC1 installed and working you should stay on that release candidate. I did that Thursday on a multisite install and a stand alone. They’re both still on RC1.

    See if that sorts it out for you.

    Moderator Jan Dembowski

    (@jdembowski)

    Brute Squad and Volunteer Moderator

    *Re-reads, posting a new post for the email*

    I manually installed 4.1RC1 over the files to fix the problem. I also deactivated the beta tester plugin.

    Later it showed there was an update to core so I ran it via the built in updater and it took me back to 4.2 alpha. This was done with the beta tester plugin deactivated.

    That’s bizzare and I’m asking other people to look at it. The deactivating the beta plugin should have stopped that from happening but obviously it didn’t for you and others.

    Moderator Jan Dembowski

    (@jdembowski)

    Brute Squad and Volunteer Moderator

    Right. First order of business.

    @luciole135 I sincerely apologize. I thought I was doing what you described when in fact I was not and I made a mistake. Thank you for reporting this.

    @andrejcarter I did a fresh install, new DB, new directories, no plugins, no additional themes. Straight fresh installation of 4.1 RC1.

    After 4.1 RC1 was installed I went to http://test-url/wp-admin/update-core.php and clicked update. I made sure not to click on “Download nightly build”, I just clicked the “Update Now” button.

    What I expected was to get 4.1 RC1. What I actually got was 4.2-alpha.

    I am convinced I am doing something wrong and I am making a basic mistake in that update. I may have misread but I do not think 4.1 RC1 should update me to the 4.2-alpha and I am asking others to look at this.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Updating takes me to 4.2-alpha’ is closed to new replies.