Running v4.0-alpha and I don't know why!

Resolved rodeboy
(@rodeboy)

9 years, 11 months ago

Hi, I have had the GB version of WordPress on a Woocommerce site I manage for a customer SallysTackShop(dot)co(dot)uk. Within Updates it showed that there was an update available and as I knew v3.9.1 was being installed on my other sites I clicked it.

Now it appears I have a version that is in the early stages of testing. I would rather not put my customers business at risk in this way, or is it stable enough to leave. I’m happy being one step ahead, but can’t afford any issues.

Secondly, any idea how the site got caught up in this?! Is it because it’s the GB version?

Thanks, Chris

Viewing 10 replies - 1 through 10 (of 10 total)

Easton Bavents
(@microbe)

9 years, 11 months ago

Snap, looks like I may have the same thing, 1-2% percentage of the sites I manage have updates to 4 alpha, looks like they are en-GB as well.

Thread Starter rodeboy
(@rodeboy)

9 years, 11 months ago

Glad I’m not alone! Now what do we do?!!

Seems like it’s an issue with the development of v4.0 in en-GB

Paul Oaten
(@pcaweb)

9 years, 11 months ago

Same thing here too. I don’t want to be running a bleeding edge version on a production ecommerce website!! WTF?

Lee Willis
(@leewillis77)

9 years, 11 months ago

See: https://core.trac.wordpress.org/ticket/28181

Paul Oaten
(@pcaweb)

9 years, 11 months ago

It’s not clear to me what’s happening with this?

Lee Willis
(@leewillis77)

9 years, 11 months ago

3.9.1 en_GB has been re-rolled apparently to resolve it.

If you have an affected site, I think you can just follow the approach here:

https://wordpress.org/support/topic/updat-wp-39-installed-40-alpha?replies=21#post-5470519

But for 3.9 read 3.9.1…

Alex Stanhope
(@247creative)

9 years, 11 months ago

Yep – happening here on a number of what were purportedly 3.9.1 “stable” installs running en-GB; the pain is that they’re all production sites!

Paul Oaten
(@pcaweb)

9 years, 11 months ago

Restored site from a backup taken pre-auto-update. Then let WP auto-update to 3.9.1 – this time it was successful.

robscott
(@robscott)

9 years, 11 months ago

Thanks @lee Willis – reverting looks like the solution here, just wanted to confirm that its a GB WP issue, not a WooCommerce problem.

Thread Starter rodeboy
(@rodeboy)

9 years, 11 months ago

If people still have this issue just to let you know that I followed the instructions given in the link proved by Lee Willis and it worked perfectly.

I did take a full backup, but this was not needed.