• Resolved Sal Ferrarello

    (@salcode)


    I have the following settings selected on /wp-admin/tools.php?page=wp-beta-tester

    • Bleeding Edge
    • Release Candidates Only

    and the message displayed is

    Currently your site is set to update to version 6.2.3, 6.3-RC1, or 6.3, whichever is released first.

    However, when I go to /wp-admin/update-core.php the button says

    Update to version 6.3-RC2

    and 6.3-RC2 is not one of the options listed on the first page.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Andy Fragen

    (@afragen)

    Sal, the message is not exact and depends upon what your current installed version is and where in the release process WP is.

    If you were already on RC1 it would say RC2. If you are on 6.2.2 and just activated those settings that’s the expected result. Once you update to the latest setting you will see more correct messaging.

    Thread Starter Sal Ferrarello

    (@salcode)

    Hi Andy ??

    Based on your explanation, the behavior makes sense.

    However in terms of user experience, listing the possible version and then updating to something that does not appear on the list is disconcerting.

    I wonder if the message could be modified to avoid this.

    i.e. instead of

    Currently your site is set to update to version 6.2.3, 6.3-RC1, or 6.3, whichever is released first.

    perhaps

    Currently your site is set to update to version 6.2.3, 6.3-RCx, or 6.3, whichever is released first.

    or

    Currently your site is set to update to version 6.2.3, 6.3-RC1, 6.3-RC2, etc. or 6.3, whichever is released first.

    or

    Currently your site is set to update to version 6.2.3, 6.3-RC1 (or higher) or 6.3, whichever is released first.

    I understand if this is a wontfix (and that might be my decision if this were my plugin ??) but in case you want to try adding “(or higher)” I’ve opened a PR at https://github.com/afragen/wordpress-beta-tester/pull/76

    Plugin Author Andy Fragen

    (@afragen)

    Hey Sal ??

    The same issue would also happen if we were in the middle of the beta cycle ??

    I’ll take a lost the PR, but you may be correct.

    Thread Starter Sal Ferrarello

    (@salcode)

    Wow, thanks for your work on the develop branch on GitHub.

    Looks good ??

    More details in this comment in GitHub.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘“Currently your site is set to update to” message is incorrect’ is closed to new replies.