dnnsoftware / Dnn.Platform

DNN (formerly DotNetNuke) is the leading open source web content management platform (CMS) in the Microsoft ecosystem.
https://dnncommunity.org/
MIT License
1.02k stars 746 forks source link

New 9.11 install - packages outdated #5346

Closed enfJoao closed 1 year ago

enfJoao commented 1 year ago

Description of bug

Brand new install of DNN 9.11. The extension manager shows this: image

image

image

Steps to reproduce

Brand new install.

Expected behavior

DNN installs latest versions of packages.

I have a couple other instalations, and this also happened to one other site (updated a couple times). The last is fine with all packages reporting latest version.

jeremy-farrance commented 1 year ago

I've noticed this subject keeps coming up. I also had the expectation that these Version/Upgrade numbers would match the latest install or upgrade - until (I believe) I was told otherwise and not to worry about it. If I am right and that it is normal and not a problem, then the problem is that we need to fix the display of information so people's expectations are met.

What can we do on that screen so that an average DNN Joe like me clearly sees that those version numbers are okay?

A big part of the problem appears to be the version numbers shown in the Upgrade column. Maybe that needs a rethink or rework? But seeing all those "9.3.2" versions is definitely counter-intuitive.

Again, I feel this needs some attention simply because I have repeatedly seen it waste time in both conversations, community discussions, and also people taking the time to report it as an issue.

enfJoao commented 1 year ago

Many many improvements needed. You can see bellow that this does not happen in all installs. Bellow is a DNN with the same version. Then, there is the random numbers and bool in the updates on the right. Finally, how can we tell if an upgrade package missed something or not?

image

image

sleupold commented 1 year ago

in your web.config file, section "appSettings", can you please compate value for key "UpdateServiceUrl"

enfJoao commented 1 year ago

<add key="UpdateServiceUrl" value="https://dnnplatform.io" /> On both

sleupold commented 1 year ago

are both apppool users able to access outside urls?

enfJoao commented 1 year ago

Can you rephrase that question to a more n00b friendly version?

On Wed, Oct 19, 2022, 17:02 Sebastian Leupold @.***> wrote:

are both apppool users able to access outside urls?

— Reply to this email directly, view it on GitHub https://github.com/dnnsoftware/Dnn.Platform/issues/5346#issuecomment-1284244557, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKKKX3G3UF22B2ICYB5VI3WEALQ5ANCNFSM6AAAAAARJC5UQ4 . You are receiving this because you authored the thread.Message ID: @.***>

enfJoao commented 1 year ago

Or is there an easy way for me to test that? One of the installs is a plesk shared account.

On Wed, Oct 19, 2022, 17:02 Sebastian Leupold @.***> wrote:

are both apppool users able to access outside urls?

— Reply to this email directly, view it on GitHub https://github.com/dnnsoftware/Dnn.Platform/issues/5346#issuecomment-1284244557, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGKKKX3G3UF22B2ICYB5VI3WEALQ5ANCNFSM6AAAAAARJC5UQ4 . You are receiving this because you authored the thread.Message ID: @.***>

mitchelsellers commented 1 year ago

We need to ensure that all core elements match expected version for clarity.

The upgrade service is on my plate to try and find a way to "fix" rogue versions.

donker commented 1 year ago

I could not replicate the original reported issue. I have installed a clean 9.11.0 and all packages were labeled as 9.11.0. I cannot explain the behavior seen by the poster with certain packages being labeled as 9.3.2. There are no older versions within the distributed zip so I can't see where that might come from.

As to the funky versions on the right: this is due to an imperfection in our upgrade service and we hope to repair this one day. It has nothing to do with your own DNN installation. These are the versions echoed by our upgrade server and they can get thrown off sometimes. We regularly go in to reset those values to what they should be.

I'm closing this issue for now and I'd invite anyone to resubmit if this can be reproduced consistently.