Diving in the code I found a few suspicious lines.
1. In the Django code, there's no mention of "repository" in this list:
https://github.com/qgis/QGIS-Django/blob/6d03c8428abe9df7634bbf810bbcb63709b11d45/qgis-app/plugins/views.py#L908
2. In the QGIS code, the PluginManager seems to look for
"code_repository" and not "repository".
https://github.com/qgis/QGIS/blob/4293d4f1c57614e0a4d3835b7d9f18b3a78bcbd1/src/app/pluginmanager/qgspluginmanager.cpp#L991
Hope this helps fixing it. I currently don't have time to setup the
Django environment and and try fixing it myself.
Raymond
On 26-01-2024 10:03, Raymond Nijssen via QGIS-Developer wrote:
Dear developers,
I found some unexpected behaviour in the plugin management.
I changed the the plugin source code to another github repository and
wanted to update the links in the plugin metadata.
1. When updating the metadata localy, and running the plugin from local
code, the metadata changelog is updated (so I know QGIS has read the
metadata.txt) but the links to the code, homepage and tracker are still
pointing to the old repository.
2. After uploading the new version of the plugin to the QGIS plugin
repository, the links to homepage and tracker are updated but the link
to the code keeps pointing to the old location. (See screenshot)
Is this a bug? If so, where should I file it?
Kind regards and happy QGIS Open Day! :)
Raymond
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer