QGIS Issue Tracking: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-05-22T12:50:42ZQGIS Issue Tracking
Redmine QGIS Plugin Site - Bug report #22123 (Open): test 1https://issues.qgis.org/issues/221232019-05-22T12:50:42ZRichard Duivenvoorde
<p>test 1</p> QGIS Plugin Site - Bug report #21715 (Open): Add "Requirements" as optional field in metadata.txthttps://issues.qgis.org/issues/217152019-03-31T16:39:36ZSfkeller -sfkeller@gmail.com
<p>As a user when searching and browsing for a plugin in QGIS extension manager or on the website <a class="external" href="https://plugins.qgis.org/">https://plugins.qgis.org/</a> , users should be informed before hand about the requirements, dependencies and restrictions of a plugin.</p>
<p>There is currently a newly added text in the "Recommendation" chapter on <a class="external" href="https://plugins.qgis.org/publish/">https://plugins.qgis.org/publish/</a> to mention requirements, dependencies and restrictions in the About/Description field, if the plugin is running only on selected platforms, requires software to be installed separately or requires some user account.</p>
<p>My suggestion is to add an optional field - perhaps called "requirements" - in metadata.txt, to be filled in by the plugin maintainer. The field entry would be mandatory if there exist such requirements.</p>
<p>Some dependencies and restrictions could even be potentially validated automatically.</p> QGIS Plugin Site - Bug report #20125 (Feedback): DIGITIZING TOOLS PLUGINhttps://issues.qgis.org/issues/201252018-10-16T16:58:54ZDaniel Roigdanielroigmaicas@gmail.com
<a name="User-Feedback"></a>
<h2 >User Feedback<a href="#User-Feedback" class="wiki-anchor">¶</a></h2>
<p>When I try to enable the Digitizing Tools connextor, QGIS always crashes.</p>
<a name="Report-Details"></a>
<h2 >Report Details<a href="#Report-Details" class="wiki-anchor">¶</a></h2>
<p><strong>Crash ID</strong>: d59fe186a1b385700807ef95060504c6369ecfd1</p>
<p><strong>Stack Trace</strong><br /><pre>
QObject::connect :
PyInit_QtCore :
PyFrame_New :
PyObject_Call :
PyInit_sip :
PyInit__gui :
PyCFunction_FastCallDict :
PyObject_GenericGetAttr :
PyEval_EvalFrameDefault :
PyErr_Occurred :
PyFunction_FastCallDict :
PyObject_CallFunctionObjArgs :
PyUnicode_AsUTF8AndSize :
PyFrame_New :
PyObject_GenericGetAttr :
PyEval_EvalFrameDefault :
PyErr_Occurred :
PyFunction_FastCallDict :
PyObject_CallFunctionObjArgs :
PyUnicode_AsUTF8AndSize :
PyFrame_New :
PyObject_GenericGetAttr :
PyEval_EvalFrameDefault :
PyObject_GenericGetAttr :
PyEval_EvalFrameDefault :
PyObject_GenericGetAttr :
PyEval_EvalFrameDefault :
PyErr_Occurred :
PyEval_EvalCode :
PyArena_Free :
PyRun_StringFlags :
instance :
instance :
QgsPluginRegistry::loadPythonPlugin :
CPLString::~CPLString :
CPLString::~CPLString :
QMetaObject::activate :
QStandardItemModel::`default constructor closure' :
QMetaObject::activate :
QAbstractItemModel::dataChanged :
QStandardItemModel::itemChanged :
QStandardItem::setData :
QStandardItemModel::setData :
QSortFilterProxyModel::setData :
QStyledItemDelegate::editorEvent :
QAbstractItemView::selectionModel :
QAbstractItemView::edit :
QAbstractItemView::mouseReleaseEvent :
QListView::mouseReleaseEvent :
QWidget::event :
QFrame::event :
QAbstractItemView::viewportEvent :
QCoreApplicationPrivate::sendThroughObjectEventFilters :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QApplicationPrivate::sendMouseEvent :
QSizePolicy::QSizePolicy :
QSizePolicy::QSizePolicy :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QGuiApplicationPrivate::processMouseEvent :
QWindowSystemInterface::sendWindowSystemEvents :
QEventDispatcherWin32::processEvents :
CallWindowProcW :
DispatchMessageW :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QDialog::exec :
PyInit__gui :
PyCFunction_FastCallDict :
PyObject_GenericGetAttr :
PyEval_EvalFrameDefault :
PyErr_Occurred :
PyObject_GenericGetAttr :
PyEval_EvalFrameDefault :
PyErr_Occurred :
PyEval_EvalCode :
PyArena_Free :
PyRun_StringFlags :
instance :
instance :
QgisApp::rotatePointSymbols :
QgsPythonRunner::run :
QgisApp::showPluginManager :
QMetaObject::activate :
QAction::activate :
QMenu::actionGeometry :
QMenu::actionGeometry :
QMenu::mouseReleaseEvent :
QWidget::event :
QMenu::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QApplicationPrivate::sendMouseEvent :
QSizePolicy::QSizePolicy :
QSizePolicy::QSizePolicy :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify :
QCoreApplication::notifyInternal2 :
QGuiApplicationPrivate::processMouseEvent :
QWindowSystemInterface::sendWindowSystemEvents :
QEventDispatcherWin32::processEvents :
CallWindowProcW :
DispatchMessageW :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main :
BaseThreadInitThunk :
RtlUserThreadStart :
</pre></p>
<p><strong>QGIS Info</strong><br />QGIS Version: 3.2.0-Bonn<br />QGIS code revision: commit:bc43194061<br />Compiled against Qt: 5.9.2<br />Running against Qt: 5.9.2<br />Compiled against GDAL: 2.2.4<br />Running against GDAL: 2.2.4</p>
<p><strong>System Info</strong><br />CPU Type: x86_64<br />Kernel Type: winnt<br />Kernel Version: 10.0.17134</p> QGIS Plugin Site - Bug report #19806 (Open): When uploading a new plugin version with metadata ch...https://issues.qgis.org/issues/198062018-09-10T12:13:37ZPaolo Cavallinicavallini@faunalia.it
<p>and it has to be changed by hand.</p> QGIS Redmine (QGIS bug tracker) - Bug report #16557 (Open): Default "Category" is blank, but cann...https://issues.qgis.org/issues/165572017-05-16T09:13:15ZSandro Santillistrk@kbt.io
<p>Filing tickets in this tracker requires picking a Category, but there's a single Category being "any" and it's not the default.<br />The default category is blank, which is invalid.</p>
<p>Please make "any" the default, if it has to stay, or allow blank Category...</p>
<p>NOTE: I'm assigning to Jurgen because I've been told it's Jurgen and Richard who worked on the upgrade, but Richard is not in the pull-down menu for Assignee...</p> QGIS Redmine (QGIS bug tracker) - Bug report #16554 (Open): Issues summary misses "Support" requestshttps://issues.qgis.org/issues/165542017-05-16T09:04:51ZSandro Santillistrk@kbt.io
<p>The <a class="external" href="https://issues.qgis.org/projects/qgis-redmine">https://issues.qgis.org/projects/qgis-redmine</a> page shows a summary of issues, but only reports "Bug report" and "Feature request" kind of issues. This means the many "Support" issues are not summarized there.</p>
<p>While filing <strong>this</strong> issue I see that the "Tracker" selection box only shows "Bug report" and "Feature request" too, so maybe the existing tickets in the "Support" tracker are just form the previous deploy ?</p> QGIS Plugin Site - Bug report #16479 (Open): "None" results in plugin search results on Django sitehttps://issues.qgis.org/issues/164792017-04-28T03:10:20ZTom Chadwintom.chadwin@nnpa.org.uk
<p>See, for example:</p>
<p><a class="external" href="http://plugins.qgis.org/search/?q=selection">http://plugins.qgis.org/search/?q=selection</a></p>
<p>Various results come back as "None", which link back to the search results page you are already on.</p> QGIS Plugin Site - Bug report #16103 (Open): Add About sections to Plugin approval notification m...https://issues.qgis.org/issues/161032017-01-23T00:54:45ZRegis Haubourgregis.haubourg@oslandia.com
<p>Hi, <br />I wonder if someone could add the "About" section in the plugin approval notifications so that we can just have a quick look on what a plugin actually does without having to explore the repository? <br />That would help a lot since plugin naming is most of the time not helpful at all. <br />Cheers</p> QGIS Plugin Site - Bug report #14913 (Open): Fresh plugin includes obsolete stuffhttps://issues.qgis.org/issues/149132016-05-27T20:49:27ZPaolo Cavallinicavallini@faunalia.it
<p>Same for other tags, that use unclear classification.<br />See <a class="external" href="http://plugins.qgis.org/plugins/fresh/">http://plugins.qgis.org/plugins/fresh/</a> <a class="external" href="http://plugins.qgis.org/plugins/most_downloaded/">http://plugins.qgis.org/plugins/most_downloaded/</a> etc.</p> QGIS Plugin Site - Bug report #10713 (Feedback): Plugin name sort order is case-sensitivehttps://issues.qgis.org/issues/107132014-06-25T00:41:40Zjtornero -
<p>Plugin name sort order is case-sensitive, so first are displayed all plugins with first uppercase letter and then those with first lowercase letter.<br />It is annoying for the user, mainly because it gives the impression of "missing plugins" when looking for one in particular.</p>
<p>Best regards</p> QGIS Plugin Site - Bug report #10142 (Open): The "repository" tag is not updated from metadata.txthttps://issues.qgis.org/issues/101422014-04-30T03:05:12ZBorys Jurgiel
<p>Steps to reproduce:<br />1. Create a plugin with missing the "repository" tag in the metadata.txt and upload it.<br />2. The application complains about the missing tag of course.<br />3. Create a new (higher) version with that tag added to the metadata.txt and upload it.<br />4. The application still says that tag is missing.</p>
<p>Please note the "homepage" and "tracker" tags work properly.</p> QGIS Plugin Site - Bug report #9930 (Open): Provide a nice user maphttps://issues.qgis.org/issues/99302014-03-28T05:46:19ZAnita Graseranitagraser@gmx.at
<p>preferable using QGIS server</p> QGIS Plugin Site - Bug report #8645 (Open): Only four stars are shown on the plugin list pagehttps://issues.qgis.org/issues/86452013-09-22T10:59:03ZAnita Graseranitagraser@gmx.at
<p>Plugins can be rated with up to five stars and on the individual plugin page, up to five stars are displayed. In the plugin list on the other hand, only a maximum of four stars is visible.</p> QGIS Plugin Site - Bug report #6617 (Open): Plugin licencehttps://issues.qgis.org/issues/66172012-11-03T21:58:47ZPaolo Cavallinicavallini@faunalia.it
<p>In most plugins there is no separate licence file, and in many there is no licence whatsoever.<br />I think this should be a requirement for accepting a plugin on the repo, and should ask authors to fix this.<br />IMHO we should establish a standard way to add it (e.g. provide a LICENSE file and put license header to all sources, probably integrating in Plugin Builder).</p>
<p>Unsure whether this is the right place to place this ticket - feel free to move it elsewhere.</p> QGIS Plugin Site - Bug report #6478 (Open): Add user commentshttps://issues.qgis.org/issues/64782012-10-07T12:04:12ZPaolo Cavallinicavallini@faunalia.it
<p>As above</p>