Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a custom QGIS repository that worked well with my own plugins.xml on a private server. Yesterday I downloaded and installed the newest QGIS-DEV that now include some changes in the Python plugins manager and I can't make my custom plugins repository work on that version... I can create the repository that effectively see my plugins.xml file but the plugins defined inside that .xml files are not shown in the available plugins list as usual...

Is this new plugin manager version completed? Does it implement custom repository or is it a work in progress?

Thanks a lot


share|improve this question
up vote 1 down vote accepted

The new plugin manager is ready for QGIS 2.0, requiring some changes in all plugins.

The qgis-dev mailing list has some advice what you have to change:

If you have to stick to your plugins, either use QGIS 1.8.0 or a previous nightly build. For Windows OS, they are saved here:

share|improve this answer
I believe the most important changes concerning this question are the change from to metadata.txt and the introduction of the metadata parameters qgisMinimumVersion and the optional qgisMaximumVersion. – Matthias Kuhn Jun 27 '13 at 13:34
There is not much to be changed, but is has to be done ;-) – AndreJ Jun 27 '13 at 14:22
As the question concerns the repository and not the API I wanted to point out the changes which led to the particular problem mentioned in the question ;-) – Matthias Kuhn Jun 27 '13 at 19:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.