@hpvd opened this Issue on February 18th 2014


Updating of plugins works fine before 2.1 RC
Now there seem to be no notification for new versions of plugins.

Please see example in attachment.

When is the status of a plugin (up to date / update available) checked?

Login logout doesn't solve it

@hpvd commented on February 18th 2014
@hpvd commented on February 19th 2014
@hpvd commented on February 21st 2014
@hpvd commented on February 18th 2014

hmm time doesn't help:
still no notification e.g.for the 1.03 security info plugin (1.02 is installed)
Not in the menu, not in the plugin table
using piwik 2.1RC3, and php 5.3.27

@hpvd commented on February 19th 2014

updated to RC4 => still no notification for available update...

@hpvd commented on February 19th 2014

Since I check for updates of Piwik and its plugins once a day and install them directly if they are available,
update notification seems not to work at least since feb 12th.
Please see attachment with new found of not up to date plugins...

@mattab commented on February 20th 2014 Member

Thanks for the report, we could reproduce. Maybe we will only fix after 2.1 release. Cheers

@hpvd commented on February 21st 2014

There seem to be changes with RC8.

  • Available updates are shown in menu again: (number)
  • but no updates are shown in table

please see attachment

@hpvd commented on February 21st 2014

after installing an update and reloading the page with the plugin table again: the notification on the top of the table is also back...

@hpvd commented on February 24th 2014

with RC9 update notification doesn't work any-more again (same as before RC8).
Only in RC8 it was temporally working nearly fine again...

@tsteur commented on February 24th 2014 Member

Fixed. All plugins on the Marketplace must have a valid semantic version number, otherwise it failed. In this case an old version of the PleineLune plugin was used which did not have any version number specified. So the core version number was used which was not a valid semantic version. I do now catch such errors to make sure the plugin update check still works for plugins having a valid version number but ignoring plugins having an invalid version number since those plugins are not installed via the marketplace.

It only occurred if someone installed a plugin manually having the same name as a plugin on the marketplace but used an invalid version number.

This Issue was closed on February 24th 2014
Powered by GitHub Issue Mirror