Local suggest to upgrade WordPress

Support
1

Why would Local briefly suggest to upgrade all websites to the latest WordPress beta version just because I have one website with the beta version?

2

Hey @emmtre!

Thank you for the video. I shared this with the team so we can take a deeper look. We haven’t come across many users testing Beta versions of WP, so this might be something new for us to dig into. Some follow-up questions here:

Have you made any changes so that WP-CLI can see the beta version as an Upgrade Option? Or something along those lines?

What happens if you click between two different sites with different WP versions and one is not a Beta? Does it flicker the last site’s WP version (regardless of Beta or not)?

Thanks!

4

@Nick-B

No, I haven’t made any such changes to WP-CLI that I can recall. Just using the command wp core update --version=6.3-beta4 to update to the latest beta. And I have also deleted all downloaded WordPress versions in ~/.wp-cli/cache/core.

It looks like the WordPress update message in the Local app is briefly displaying the previous selected website WordPress version before displaying the correct update message (none or “Update to 6.2.2”) for the current selected website. But only for beta versions.

Here are a few scenarios.

  1. Website A with 6.2.2 is first selected. No update message.
    Then selecting website B with 6.2.2. No update message.
  2. Website C with 6.1.3 is first selected. Message “Update to 6.2.2”.
    Then selecting website A with 6.2.2. No update message.
  3. Website A with 6.2.2 is first selected. No update message.
    Then selecting website C with 6.1.3. Message “Update to 6.2.2”.
  4. Website A with 6.2.2 is first selected. No update message.
    Then selecting website D with 6.3-beta4. No update message.
  5. Website D with 6.3-beta4 is first selected. No update message.
    Then selecting website A with 6.2.2. Message “Update to 6.3-beta4” briefly and then no update message.
  6. Website D with 6.3-beta4 is first selected. No update message.
    Then selecting website C with 6.1.3. Message “Update to 6.3-beta4” briefly and then message “Update to 6.2.2”.
5

Hi @emmtre

Circling back here so you know we aren’t leaving you hanging. I shared this with the team and they aren’t quite sure what the root cause is so we’ll get a bug submitted to dig in. No ETA to provide on this but we’ll definitely let you know if we have any questions or follow-up!

1 Like
6

@Nick-B Many thanks for the update. Have you managed to confirm the same behavior when you have installed a website with a WordPress beta or release candidate? For me it’s the same behavior with php 8.2 and 6.3-rc1. Just an annoying graphical glitch. The update version in the message must be cached somewhere. Or a bad version logic that doesn’t expect the text beta or rc at the end.

1 Like
7

I just tested this and I was able to replicate it! It’s definitely some type of bug or UI glitch that hasn’t come up yet, so we’re glad for you bringing it to our attention. We’ve created a ticket to look into this further and figure out what’s going on. :green_heart:

1 Like
8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.