I now have 4.2 alpha 1 !!!!

*Drinks coffee*

Something updated it. The WordPress 4.1 RC1 will not do that by itself.

Double check your plugins and host, if it still continues then please start your own topic with your details.

https://www.ads-software.com/support/forum/how-to-and-troubleshooting#postform

That’s the best way for you to get assistance, as this forum and topic really is not for troubleshooting. It’s for the alpha/beta testing.

I have not installed and enabled a single plugin, it is a local test version installed with XAMPP, but with WAMP the problem is the same.

That really sounds bizzare and something is doing that. Have you posted a new topic and shared the details there?

https://www.ads-software.com/support/forum/how-to-and-troubleshooting#postform

As I’ve mentioned, this is the wrong sub-forum and not your topic. ??

I’m having the same issue with updating to 4.2 alpha without the beta tester plugin activated and created a new topic as suggested – https://www.ads-software.com/support/topic/updating-takes-me-to-42-alpha.

I won’t get into the opening of a discussion of support because I do not speak English well enough. I reported a problem that you can easily test by installing yourself a local version of WordPress on your computer with wordpress 4.1 RC1.

It seems illogical to me that 4.2 Alpha 1 exists before 4.1 has been released.
I can understand the nightly build going to 4.2 Alpha 1 After 4.1 has been released but not before….
Is my thinking flawed ?
Cheers, Dave

When you install any of the alpha, beta or RC versions of WordPress the version checker will look for updates against the nightly builds.

The nightly builds are always built from trunk, which currently holds the version number 4.2-alpha. This means you’ll have all the 4.1-RC features (and from a technical view point still be on 4.1-RC), even if the version string during this period shows the alpha one (they’re essentially the same up until release with the exception of the version string).

We’re aware that it’s a little bit confusing as we’ve not increased the version number on trunk this early in the RC cycle before, but don’t worry, you’re still testing 4.1-RC at this point, and you are getting any patches made for 4.1.

The expected behavior of the BETA tester plugin is to install an ALPHA? That’s silly. If that’s in fact the case can the RC announcement post be updated to make that clear? And the name of the plugin changed too?

On another note, when the real version of 4.1 is released will I be able to update to it using the built in updater on my installation that is currently saying it’s on 4.2 alpha (with the Alpha/Beta tester plugin deactivated)?

The expected behavior of the BETA tester plugin is to install an ALPHA? That’s silly.

The expected behavior of the beta tester plugin is to install the nightlies when configured that way. The nightlies at this moment are set to 4.2-alpha.

On another note, when the real version of 4.1 is released will I be able to update to it using the built in updater on my installation that is currently saying it’s on 4.2 alpha (with the Alpha/Beta tester plugin deactivated)?

I don’t think so but when 4.1 is released I will confirm that. I am 99.994% sure that you will need to manually install 4.1 when it is released.

I show 2 options for the Beta Tester plugin at wp-admin/tools.php?page=wp_beta_tester. The first is Point Release Nightlies and the other is Bleeding Edge Nightlies. Which should I have it set to if I want Beta or RCs without Alphas?

The beta tester plugin wont put you on the RC. Currently the nightlies are set to the 4.2-alpha so if you use the beta tester plugin then you won’t get the version you want.

Thank you. Is this the expected behavior for future releases also?

Yes. What’s happened is that the beta test plugin is using the latest nightlies and that’s what is supposed to do. At some point the nightly switches to the next alpha.

Previously I used SVN and switched to the plugin a few releases ago. I can’t recall if this happened last time but I don’t see went it wouldn’t and that’s why some don’t use this plugin.

This is the first release cycle that the Beta Tester plugin has led me to an alpha, which is why I questioned it. It didn’t match my expectations or past experiences.

So what’s the recommended way to test Betas and RCs? Download the zip and FTP?

You said:

So what’s the recommended way to test Betas and RCs? Download the zip and FTP?

I said 13 hours ago this:

I just manually reinstall RC1. Then, I manually downloaded wordpress-latest and I installed it manually. I get new 4.2-alpha!
There’s a big problem!

You can try, you’ll have the same result, you’ll install 4.2-alpha also.