Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"Check for updates" does not check for plugins updates on Marketplace #9065

Closed
mattab opened this issue Oct 20, 2015 · 3 comments
Closed

"Check for updates" does not check for plugins updates on Marketplace #9065

mattab opened this issue Oct 20, 2015 · 3 comments
Assignees
@tsteur
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone
2.16.0

Comments

@mattab
Copy link
Member

mattab commented Oct 20, 2015

At this moment on demo.piwik.org we use version 0.1.1 of plugin AnonymousPiwikUsageMeasurement. A new version 0.1.2 was released few minutes ago. After clicking Check for updates in the top right selector in admin area, the new plugin update is still not displayed as available.

Expected behavior: Check for updates button should reset the cache for Piwik core version but also all plugins installed from the marketplace.
@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Oct 20, 2015
@mattab mattab modified the milestone: 2.15.0 Oct 20, 2015
@mattab
Copy link
Member Author

mattab commented Oct 20, 2015

it's possible that this occured because the plugin was disabled. Maybe the plugin update check does not check for disabled plugins? (I think it should, if not already)

@tsteur
Copy link
Member

tsteur commented Oct 20, 2015

I had a look and we usually do invalidate the marketplace cache when checking for updates.

Possibly it's because it is disabled then

tsteur added a commit that referenced this issue Nov 18, 2015
@tsteur
refs #9065 show plugin updates for disabled plugins
8d483ec
@tsteur tsteur mentioned this issue Nov 18, 2015
Merged
@tsteur
Copy link
Member

tsteur commented Nov 18, 2015

I can confirm it was because the plugin was disabled see PR in #9235

@mattab mattab added this to the 2.15.1 milestone Nov 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tsteur tsteur

Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Milestone
2.16.0
Development

No branches or pull requests
2 participants
@tsteur @mattab