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

New version of plugins from 3rd party repo does not appear #25308

Closed
qgib opened this issue Nov 7, 2017 · 3 comments
Closed

New version of plugins from 3rd party repo does not appear #25308

qgib opened this issue Nov 7, 2017 · 3 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins

Comments

@qgib
Copy link
Contributor

qgib commented Nov 7, 2017

Author Name: Saber Razmjooei (@saberraz)
Original Redmine Issue: 17411
Affected QGIS version: 2.18.14
Redmine category:python_plugins
Assignee: Borys Jurgiel


There seems to be a problem with QGIS cache when reading data from 3rd party plugin repo.

The xml file shows there is a new version. But QGIS plugin manager does not see the new version. Deleting cache folder will solve the problem. But clearing the cache should be done as a part of Reloading Plugin repos.

@qgib
Copy link
Contributor Author

qgib commented Jan 4, 2018

Author Name: Borys Jurgiel (@borysiasty)


Hi Saber,

I believe QGIS only uses the cache if the http response header contains @cache-control:max-age=NNNNNN@. Could you please confirm the affected repo actually adds it? If I'm right, it's enough to just fix the http server configuration. Otherwise could you send me the headers?

By the way, we can tell plugin installer to ignore the header directive (no need to clear all the cache), but I'm not convinced to force downloading every repository, even if it doesn't want to be reloaded. Some people already complain for the repo fetching time :)


  • assigned_to_id was configured as Borys Jurgiel

@qgib
Copy link
Contributor Author

qgib commented Jan 5, 2018

Author Name: Saber Razmjooei (@saberraz)


Thanks Borys. It was indeed due to Cache-Control:max-age on our server. We will change that.


  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Jan 5, 2018
@qgib
Copy link
Contributor Author

qgib commented Feb 22, 2018

Author Name: Giovanni Manghi (@gioman)


  • resolution was changed from to invalid

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Plugins
Projects
None yet
Development

No branches or pull requests

1 participant