Show current version when upgrade pending #2826

anonymous-piwik-user opened this Issue Dec 15, 2011 · 5 comments

3 participants


I don't look at my Piwik dashboard very often. When I do and see that Piwik wants to upgrade, I look at the changelog first. I'm always wondering how far back I need to scan to see what changed between what I have and the latest version, but without an easy way to see the current Piwik version this is difficult.

I did find that I could navigate to piwik/Core/Updates and figure this out from the latest version-named file, but this is not the most user-friendly thing to have to do.

After upgrading, I saw that the current Piwik version is displayed in the same location that the upgrade notice was shown. All that would be required would be for the current version number to be displayed as well when an upgrade is available (it could be in the 'hover' message to avoid cluttering the screen display).

I wasn't sure whether this is a Core or UI issue so I left it as Core, since the Updates folder was under piwik/Core. Please feel free to reassign the Component as you see fit.

Piwik Open Source Analytics member

See What version of Piwik do I use?

THanks for the suggestion!


Thanks for the tip - I guess I should have tried searching for just "version" on the Piwik website (I tried "how to find version of current install") - but strange that the search I ran didn't get the relevant entry near the top of the list!

However, as I mentioned above, the normal place to see the version on the web page is supplanted when there's an upgrade pending and it's inconvenient to have to go to the server and check the contents of a file to find out the current version.

Thanks again!


If this is implemented, it should only display the version number to a logged in user. (Not anonymous.)


good point!

Piwik Open Source Analytics member

(In [5607]) Fixes #2826

@anonymous-piwik-user anonymous-piwik-user added this to the 1.7 Piwik 1.7 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment