The issue with the Extensions list is that it shows any newer version of a module DNN has "seen".
So if I fork the HTML module (locally) and build it as version 99.99.99, there's a chance hat you will see that version in the extensions list..

Posted By Craig Mitchell on 4/25/2026 8:56 AM

Hi all. anyone know what when u click the update link to the newer module versions it never takes u to where that version showing is.  Lots of examples

Craig

I think you are seeing these "fake" versions due to DNN telemetry picking up "news" of a version that really doesn't exist or hasn't been released. 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.