Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: new version is prompted but not released yet #5990

Open
2 tasks done
zyhfish opened this issue Mar 2, 2024 · 1 comment
Open
2 tasks done

[Bug]: new version is prompted but not released yet #5990

zyhfish opened this issue Mar 2, 2024 · 1 comment

Comments

@zyhfish
Copy link
Contributor

zyhfish commented Mar 2, 2024

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

When I installed 9.13.2, there is a prompt on the persona bar to show that 9.13.3 is available but currently the version hasn't been released yet, we only have the RC release.

Steps to reproduce?

  1. Install 9.13.2.
  2. Check the persona bar.

Current Behavior

2024-03-02_080927

Expected Behavior

we should only prompt for the final releases.

Relevant log output

No response

Anything else?

No response

Affected Versions

9.13.2 (latest release)

What browsers are you seeing the problem on?

Chrome

Code of Conduct

  • I agree to follow this project's Code of Conduct
@johnhenley
Copy link
Contributor

I think you are seeing these "phantom" versions due to DNN telemetry picking up "news" of a version that really doesn't exist or hasn't yet been released.

In this case 9.13.3 has just been released and you got an early notification:)

DNN has a "phone home" mechanism that sends versions for the platform and installed modules back to dnnplatform.io with the intention of collecting and corellating version information across the platform's ecosystem and sharing that information with the vendors and community. What sometimes happens though, is that a module developer might have DNN installed and be working on a module's repository (or fork of a module repository) and bumps the version in their internal build/version. But since they don't know about or perhaps forget to turn off this feature, their "update" makes its way into the telemetry, and gets pushed out to the ecosystem as a potential new version.

How do I know this? Because I've caused false updates to appear as available because I test the community forums builds on a dev version of my production site, and I forget to remove the option. :)

So yes it is frustrating. When you see a new module listed, visit the vendor or, if it's a community-built module,
https://github.com/DNNCommunity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants