I have a selection of python plugins (one rather large one) that I have developed under Qgis 1.8 and that I am migrating to qgis 2.0. The error that the Plugin Manager gives me when I load these plugins (This plugin was developed under 1.x) is rather unhelpful. It also arises in situations that have nothing to do with the API Version. For instance, a Network error yesterday introduced a stream of random characters into a few of my code files (Fun!) and this led to the Plugin Manager telling me my plugin was old. Eventually, after pain, I found out a tab and a dollar sign had been inserted in front of a comment in my metadata.txt, and that was the Problem. Screwed up, yes. Old, no.

Is there any way to see a more detailed error when QGIS 2 rejects a plugin as 1.x? If not a proper trace, then at least what class, or even what file was rejected? Anything?

The instructions regards API changes at the Qgis Hub Wiki are lovely and I sleep with them under my pillow, but they are not as lovely as a simple error message.

Qgis 2, by the way, is beautiful. Thank you.

  • Did you change your QGisMinimumVersion tag according to this (hub.qgis.org/wiki/17/…) ? – Curlew Oct 31 '13 at 9:21
  • Yes, in fact my first step in migration is to use QGIS 2.0's version of Plugin Builer to rebuild the basic plugin, and then copy in my code in piece by piece, modifying as I go according to the wiki. So, the metadata.txt I don't even mess with, and it has just what QGIS 2 wants. Once I removed the random characters from the comments, the plugin was recognized as being of the proper version. So, I understand the migration process, I just want to know how to see some real errors when QGIS thinks my plugin is old. – MonsterMushroom Oct 31 '13 at 9:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.