WordPress.org

Make WordPress Core

Opened 8 months ago

Closed 8 months ago

Last modified 7 months ago

#51679 closed defect (bug) (fixed)

All sites on alpha

Reported by: webshaun Owned by:
Milestone: 5.5.3 Priority: normal
Severity: normal Version: 5.5.2
Component: Upgrade/Install Keywords:
Focuses: Cc:

Description

Suddenly my customers websites across multiple platforms are upgrading to WordPress 5.5.3-alpha-49449

Change History (52)

#1 @mrwweb
8 months ago

I'm seeing this as well, as are other folks.

#2 @garubi
8 months ago

Yes I can confirm it

#3 @johnbillion
8 months ago

Thanks for the report folks, the wordpress.org systems team have been notified and are working on a fix.

This ticket was mentioned in Slack in #forums by richard_korthuis. View the logs.


8 months ago

#5 @lightsoutdave
8 months ago

I have confirmed it on over 20 sites I've updated in the last hour. All either production sites or git repository copies used to push to production sites.

#6 @anpor
8 months ago

All my sites are now on the developer branch and updated to the latest alpha. This seems so be a bigger issue.

#7 follow-up: @johnbillion
8 months ago

It's worth noting that there's no functional difference between 5.5.2 and 5.5.3-alpha, so there's no need to worry in that regard.

The systems team have fixed the auto update change that triggered this. More info to follow.

#8 @paulstenning
8 months ago

How do we get our sites off of developer branch if they have been switched onto it by this update issue?

#9 @ricks03
8 months ago

I'm seeing this too. So much for generating faith in automatic updates.

How do I explicitly disable development updates?

#10 @paulstenning
8 months ago

I have added this to wp-config.php on all our sites for now to avoid any more issues over the weekend

define( 'WP_AUTO_UPDATE_CORE', false );

#11 follow-up: @pcdeveloper
8 months ago

Confirmed. A WordPress just lost confidence in automatic updates because of an inattentiveness of an inattentive programmer.

#12 follow-up: @physion1
8 months ago

So do we have a fix yet?

This ticket was mentioned in Slack in #core by dhrrob. View the logs.


8 months ago

#14 @tinpeas
8 months ago

I'm seeing the "BETA TESTERS: This site is set up to install updates of future beta versions automatically." message has now disappeared.

#15 in reply to: ↑ 12 ; follow-up: @hellofromTonya
8 months ago

Replying to physion1:

So do we have a fix yet?

Yes, the systems team have fixed the auto update change that triggered this. We have confirmation from reports in slack that it fixed the problem for others.

Can you confirm that it resolves the issue for you?

#16 @skarweb
8 months ago

Same here.
And all sites have all old themes Twenty Ten until Twenty Twenty installed due to this upgrade :(

#17 in reply to: ↑ 11 @paulstenning
8 months ago

Replying to pcdeveloper:

Confirmed. A WordPress just lost confidence in automatic updates because of an inattentiveness of an inattentive programmer.

The worrying thing is that a single developer can do this, seemingly without any checking or confirmation by other developers. This is a serious security concern as a rogue developer could push out malicious code in an update that nobody else checks...

Last edited 8 months ago by paulstenning (previous) (diff)

#18 in reply to: ↑ 15 ; follow-up: @ricks03
8 months ago

Replying to hellofromTonya:

Replying to physion1:

So do we have a fix yet?

Yes, the systems team have fixed the auto update change that triggered this. We have confirmation from reports in slack that it fixed the problem for others.

Can you confirm that it resolves the issue for you?

How do I confirm it's resolved? My sites are already updated. What is the expected resolution?

#19 in reply to: ↑ 7 ; follow-up: @slewisma
8 months ago

Replying to johnbillion:

It's worth noting that there's no functional difference between 5.5.2 and 5.5.3-alpha, so there's no need to worry in that regard.

The systems team have fixed the auto update change that triggered this. More info to follow.

No functional difference? Yes, there is. The affected sites now have all twenty- themes installed.

#20 in reply to: ↑ 18 @physion1
8 months ago

I also want to know what the expected resolution is

Replying to ricks03:

Replying to hellofromTonya:

Replying to physion1:

So do we have a fix yet?

Yes, the systems team have fixed the auto update change that triggered this. We have confirmation from reports in slack that it fixed the problem for others.

Can you confirm that it resolves the issue for you?

How do I confirm it's resolved? My sites are already updated. What is the expected resolution?

#21 @sterndata
8 months ago

What is the expected resolution? <<

Go to DASHBOARD->UPDATES and click the button to reinstall 5.5.2

#22 @johnbillion
8 months ago

#51681 was marked as a duplicate.

#23 follow-up: @beavis82
8 months ago

So we have to manually roll back all our affected sites, as well as uninstall 10 themes and one plugin that were installed automatically without our permission?

Not so big a deal for people with only one or two sites, but what about agencies that are managing sometimes hundreds of sites?

#24 in reply to: ↑ 19 @paulherzlich
8 months ago

Replying to slewisma:

Replying to johnbillion:

It's worth noting that there's no functional difference between 5.5.2 and 5.5.3-alpha, so there's no need to worry in that regard.

The systems team have fixed the auto update change that triggered this. More info to follow.

No functional difference? Yes, there is. The affected sites now have all twenty- themes installed.

And your site thinks it is going to get nightly developer builds\\

#25 follow-up: @Yworld
8 months ago

You are using a development version of WordPress, it can be updated to the latest nightly build automatically:
No upgrade to 5.5.2 ru

#26 follow-up: @paulstenning
8 months ago

So basically the expected resolution is that we have to manually rollback and manually uninstall the themes this bodged update installed? Lots of work for every WordPress user.

How do we ensure we don't get future alpha and beta builds if this update changed some setting somewhere?

#27 @cdcidevel
8 months ago

This CHALLANGE is WAY WAY worse that first expected.

First 5.5.3-alpha-49449 is activating deactivated plugs, which is riddling my database with unwanted entries.

Next is has installed all the Twenty "Year" themes and all their translations.

How do we turn auto update OFF and get off this bug ridden untested branch?

How is something like this allowed to happen? We need the ability to turn all this OFF!

#28 in reply to: ↑ 25 @paulherzlich
8 months ago

Replying to Yworld:

You are using a development version of WordPress, it can be updated to the latest nightly build automatically:
No upgrade to 5.5.2 ru

Exactly what I don't want. I don't want any developer builds. I want the last good live tested build.

#29 in reply to: ↑ 23 ; follow-ups: @lightsoutdave
8 months ago

Replying to beavis82:

So we have to manually roll back all our affected sites, as well as uninstall 10 themes and one plugin that were installed automatically without our permission?

Not so big a deal for people with only one or two sites, but what about agencies that are managing sometimes hundreds of sites?

I've checked several of my sites and they're now reporting properly as 5.5.2 with "You have the latest version of WordPress." I didn't reinstall/roll them back or run any updates on them. The response from the version check is now correct. Also, my git commits are all reporting as:
"nothing to commit, working tree clean
Everything up-to-date"

It doesn't look like you'll need to manually roll back anything.

Last edited 8 months ago by lightsoutdave (previous) (diff)

#30 in reply to: ↑ 26 @hellofromTonya
8 months ago

Replying to paulstenning:

So basically the expected resolution is that we have to manually rollback and manually uninstall the themes this bodged update installed? Lots of work for every WordPress user.

How do we ensure we don't get future alpha and beta builds if this update changed some setting somewhere?

No need to rollback. Yes, the bundled themes you don't want will need to be deleted.

Last edited 8 months ago by hellofromTonya (previous) (diff)

#31 in reply to: ↑ 29 @hellofromTonya
8 months ago

Replying to lightsoutdave:

I've checked several of my sites and they're now reporting properly as 5.5.2 with "You have the latest version of WordPress." I didn't reinstall/roll them back or run any updates on them. The response from the version check is now correct. Also, my git commits are all reporting as:
"nothing to commit, working tree clean
Everything up-to-date"

It doesn't look like you'll need to manually roll back anything.

Thank you for confirming.

#32 @Yworld
8 months ago

WordPress 5.5.3-alpha-49449
You are using a development version of WordPress, it can be updated to the latest nightly build automatically:
What to do?

Last edited 8 months ago by Yworld (previous) (diff)

#33 in reply to: ↑ 29 ; follow-up: @beavis82
8 months ago

Replying to lightsoutdave:

Thanks for the update, we'll still need to remove all those extra themes though.

Really hoping WordPress release some information about how this happened and what steps will be taken to prevent this from happening again in future, as this will surely have damaged confidence in auto updates.

#34 in reply to: ↑ 33 @hellofromTonya
8 months ago

Replying to beavis82:

Really hoping WordPress release some information about how this happened and what steps will be taken to prevent this from happening again in future, as this will surely have damaged confidence in auto updates.

At the moment, the team is actively working on a 5.5.3 release to address #51676.

Information for this ticket and that one will be coming. Please stay tuned.

#35 follow-up: @hellofromTonya
8 months ago

The 5.5.3-alpha issue is a side effect of another issue that occurred on 5.5.2. There will be an announcement on WordPress.org.

#36 in reply to: ↑ 29 @ricks03
8 months ago

Replying to lightsoutdave:

Replying to beavis82:

So we have to manually roll back all our affected sites, as well as uninstall 10 themes and one plugin that were installed automatically without our permission?

Not so big a deal for people with only one or two sites, but what about agencies that are managing sometimes hundreds of sites?

I've checked several of my sites and they're now reporting properly as 5.5.2 with "You have the latest version of WordPress." I didn't reinstall/roll them back or run any updates on them. The response from the version check is now correct. Also, my git commits are all reporting as:
"nothing to commit, working tree clean
Everything up-to-date"

It doesn't look like you'll need to manually roll back anything.

Although you'll also want to delete all the twenty* themes that were installed that weren't there before.

#37 in reply to: ↑ 35 ; follow-up: @Yworld
8 months ago

Replying to hellofromTonya:

The 5.5.3-alpha issue is a side effect of another issue that occurred on 5.5.2. There will be an announcement on WordPress.org.

I still have 5.5.3-alpha-49449 and no update
Should I do nothing now?

#38 in reply to: ↑ 37 ; follow-ups: @hellofromTonya
8 months ago

Replying to Yworld:

I still have 5.5.3-alpha-49449 and no update
Should I do nothing now?

There are 2 options to resolve:

  1. Click the Re-install WordPress button on the Update screen to reinstall 5.5.2
  2. Wait to update when 5.5.3 is released (coming soon)

Please note, 5.5.3-alpha-49449 also installed bundled themes. Any of these themes the site doesn't need will need to be deleted manually.

Last edited 8 months ago by hellofromTonya (previous) (diff)

#39 in reply to: ↑ 38 ; follow-up: @Yworld
8 months ago

Replying to hellofromTonya:

Replying to Yworld:

I still have 5.5.3-alpha-49449 and no update
Should I do nothing now?

There are 2 options to resolve:

  1. Click the Re-install WordPress button on the Update screen to reinstall 5.5.2
  2. Wait to update when 5.5.3 is released (coming soon)

Please note, 5.5.3-alpha-49449 also installed bundled themes. Any of these themes the site doesn't need will need to be deleted manually.

Thank you very much!

#40 @essjay88
8 months ago

I have multiple notifications about client sites, first one I checked has 10 (yes TEN) themes installed in addition to my own Divi and Divi Child Theme) and a message saying "You are using a development version (5.5.3-alpha-49449). Cool!" No, that is very UNCOOL. Got my work cut out this weekend obviously!

#41 in reply to: ↑ 39 ; follow-up: @stephenturner
8 months ago

Hi, i'm not very technical, can you confirm if i do nothing, when 5.5.3 gets released, my sites that have just updated to the beta will be installed with 5.5.3 and then all good, ie, i will not be a beta test so in effect can just wait for the 5.5.3 update?

#42 @johnbillion
8 months ago

  • Milestone changed from Awaiting Review to 5.5.3

@stephenturner Yes that's correct. When 5.5.3 is released, you'll be updated to that stable version and you won't be alpha or beta testing from that point onward.

#43 in reply to: ↑ 41 @ricks03
8 months ago

Replying to stephenturner:

Hi, i'm not very technical, can you confirm if i do nothing, when 5.5.3 gets released, my sites that have just updated to the beta will be installed with 5.5.3 and then all good, ie, i will not be a beta test so in effect can just wait for the 5.5.3 update?

Except you'll still have the extra themes installed if you do nothing.

#44 follow-up: @CyberCr33p
8 months ago

How many MB does the extra themes use?

#45 in reply to: ↑ 44 @pidengmor
8 months ago

Replying to CyberCr33p:

How many MB does the extra themes use?

As a guide, Twenty-Twenty is 1.8 MB.

#46 in reply to: ↑ 38 @david1011
8 months ago

J'aimerai pouvoir le faire mais la mise à jour me propose uniquement la version WP en US. Alors que je la veux en FR (français).
Avez vous une solution ?
Ou est ce que restaurer mon hébergement à le jour d'avant
ou deux jours avant suffirait ? Ou est ce que je recevrai à nouveau automatiquement cette mise à jour Alpha ?

Merci pour vos réponses

Replying to hellofromTonya:

Replying to Yworld:

I still have 5.5.3-alpha-49449 and no update
Should I do nothing now?

There are 2 options to resolve:

  1. Click the Re-install WordPress button on the Update screen to reinstall 5.5.2
  2. Wait to update when 5.5.3 is released (coming soon)

Please note, 5.5.3-alpha-49449 also installed bundled themes. Any of these themes the site doesn't need will need to be deleted manually.

#47 follow-up: @audrasjb
8 months ago

@david1011

Bonjour,

Vous pouvez mettre à jour en version EN, cela mettra à jour WordPress mais votre installation restera en français. Inutile de restaurer une mise à jour. Vous êtes en réalité sur WordPress 5.5.2. C'est juste qu'il est marqué 5.5.3-alpha, mais la version est en réalité 5.5.2.

Sinon, vous pouvez aussi attendre la vraie version 5.5.3 qui arrivera cette nuit. Pas la peine de faire davantage, votre site ne court aucun risque.

(ps : je suis français comme vous mais sur cet espace il est d'usage d'utiliser l'anglais uniquement :)

Bonne soirée,
Jean-Baptiste

#48 in reply to: ↑ 47 @david1011
8 months ago

Good evening Jean Baptiste,

Nice to read your answer!
I'm gonna wait like you adviced me.
I hope tomorrow, it will be fixed.

Excuse me for my English : he's not very well. If I must use it here, I will do it.

Thanks a lot
Good evening too!

Replying to audrasjb:

@david1011

Bonjour,

Vous pouvez mettre à jour en version EN, cela mettra à jour WordPress mais votre installation restera en français. Inutile de restaurer une mise à jour. Vous êtes en réalité sur WordPress 5.5.2. C'est juste qu'il est marqué 5.5.3-alpha, mais la version est en réalité 5.5.2.

Sinon, vous pouvez aussi attendre la vraie version 5.5.3 qui arrivera cette nuit. Pas la peine de faire davantage, votre site ne court aucun risque.

(ps : je suis français comme vous mais sur cet espace il est d'usage d'utiliser l'anglais uniquement :)

Bonne soirée,
Jean-Baptiste

#49 @hellofromTonya
8 months ago

  • Resolution set to fixed
  • Status changed from new to closed

As noted, systems team fixed this issue. Post and announcement will be published shortly.

#50 @hellofromTonya
8 months ago

5.5.3 has now been released. Here is the announcement which includes more information about the issue reported in this ticket, ie 5.5.3-alpha Issue.

#51 @SergeyBiryukov
7 months ago

  • Component changed from General to Upgrade/Install

#52 @SergeyBiryukov
7 months ago

#51711 was marked as a duplicate.

Note: See TracTickets for help on using tickets.