Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Following up on Previous Ticket - Need info on cause of issue
-
Hi Support,
In a previous support request (EDO-6132). The issue then was as stated below. The All Versions tab wasn't displaying post-upgrade on our local ProGet instance.
Our concern is that this took over a day for those tabs to display the package versions post-upgrade. We cannot move forward in upgrading our Test and Production servers because that down-time is too long for our business. We want to understand why this might happen and if it can be avoided in the future upgrade.
Please let us know what additional details you might need.
Thank you,
Alex
Prior to upgrading our ProGet Prod and Test, we did a local install of our current version (5.1.4) to 5.2.7. Post-install, we cannot find the "All Versions" tab in our packages. On the main Feeds page, it lists the number of packages for each feed and the total number of versions correctly. And we see all the package in the folder directories. Yet we do not see them on the package pages. Are you able to assist?
We list this as minor, but it's a major issue if we cannot upgrade with all versions. We are on a ProGet Basic license.
-
Here's the response that @jrasch posted to that ticket;
The All Versions tab should definitely still be there, and the only case I could see where it's hidden is for the feed type of "Docker" which does not use versions.
Can you try:
- Hard browser refresh e.g. CTRL + F5
- Verify that you are logged in and not browsing anonymously
Is that what you're looking for?
Basically it sounds like it was an issue of either not being logged in, or some old Javascript cached in your browser? It's hard to say, because you had responded in the ticket that it was resolved...
-
@apxltd said in Following up on Previous Ticket - Need info on cause of issue:
Is that what you're looking for?
We had done the refresh post-upgrade, and I had been logged in with my account.
The javascript cache I haven't confirmed. I am going to perform the upgrade again locally and rule out all these factors.
Thanks.
-
I ran the full install again and realized it was the cached images in Chrome causing the issue. IE was fine, so I knew immediately it was Chrome.
Thank you again!
