QGIS Issue Tracking: Issueshttps://issues.qgis.org/https://issues.qgis.org/favicon.ico2019-05-22T07:16:59ZQGIS Issue Tracking
Redmine QGIS Application - Bug report #22120 (Open): Field_name in actionshttps://issues.qgis.org/issues/221202019-05-22T07:16:59ZAlessandro Peregoalsper78@gmail.com
<p>(tested on QGIS 3.4.8 on Windows 10)</p>
<p>Actions in field scope have three variables: field_index, field_name, field_value.<br />Field_name doesn’t work when actions run from attribute table.</p>
<p>For example the following python action (in field scope):</p>
<p>from qgis.PyQt import QtWidgets<br />expr = '"[% @field_name <span>]"' + ' = ' + "'[</span> @field_value <span>]'" <br />QtWidgets.QMessageBox.information(None, "[</span> @field_name %]", expr)</p>
<p>works good from Identify Result panel, but when the action run from the attribute table it doesn’t show the name of the field.</p>
<p>A workaround is using the field index:<br />layer = QgsProject.instance().mapLayer('[% @layer_id <span>]')<br />field_name = layer.fields().field([</span> @field_index %]).name()</p> QGIS Application - Bug report #21988 (Open): [processing][xyz tiles] De-activate folder/file bas...https://issues.qgis.org/issues/219882019-05-03T12:29:11ZSaber Razmjooeisaber.razmjooei@lutraconsulting.co.uk
<p>Currently, if user selects director or MBTiles, both output paths are activated. Best, to deactivate the unused one.</p> QGIS Application - Bug report #21972 (Open): inside the Layer's panel, can't see if a layer is ch...https://issues.qgis.org/issues/219722019-05-02T08:29:22Zc mcle.ine@free.fr
<p>inside the layer's panel, at each beginning of line (1 line = 1 layer)<br />there's a checkbox, in black & white.<br />as the whole line can be highlighted (in dark blue) when you click on it, you can't see if this layer is checked or not any more.</p>
<p>see attached snapshot</p> QGIS Application - Bug report #21936 (Open): Snapping Settings window with Night Mapping, low rea...https://issues.qgis.org/issues/219362019-04-26T10:24:52ZNicklas Larssonn_larsson@yahoo.com
<p>The Snapping Settings window has an inconsistent layout and partly very difficult to read due to low contrast with Night Mapping theme (at least on macOS).</p>
<p>This is the present layout:<br /><img src="https://issues.qgis.org/attachments/download/14850/Screenshot.png" alt="" /></p>
<p>Suggested changes:</p>
<p>1. The checkboxes (Layer and Avoid intersection) should be dark grey not black<br />2. The checkmark in Layer should be light grey<br />3. The Layer name should be dark or light grey depending on checked or not</p>
<p><img src="https://issues.qgis.org/attachments/download/14851/Mockup.png" alt="" /></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 #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 Application - Bug report #17980 (Open): "resources/data/world_map.shp" should be only access...https://issues.qgis.org/issues/179802018-01-27T14:33:45ZJohannes Kroeger
<p>QGIS tells me<br /><pre>
Warning 4: Failed to open /opt/qgis-git/share/qgis/resources/data/world_map.shp, Permission denied.
</pre></p>
<p>The file exists and is world readable<br /><pre>
-rw-r--r-- 1 root root 528032 Jan 23 23:06 /opt/qgis-git/share/qgis/resources/data/world_map.shp
</pre></p>
<p>strace suggests that QGIS is trying to access the file with write access.<br /><pre>
openat(AT_FDCWD, "/opt/qgis-git/share/qgis/resources/data/world_map.shp", O_RDONLY) = 76
openat(AT_FDCWD, "/opt/qgis-git/share/qgis/resources/data/world_map.shp", O_RDWR) = -1 EACCES (Permission denied)
stat("/opt/qgis-git/share/qgis/resources/data/world_map.shp", {st_mode=S_IFREG|0644, st_size=528032, ...}) = 0
stat("/opt/qgis-git/share/qgis/resources/data/world_map.shp", {st_mode=S_IFREG|0644, st_size=528032, ...}) = 0
openat(AT_FDCWD, "/opt/qgis-git/share/qgis/resources/data/world_map.shp", O_RDONLY) = 76
stat("/opt/qgis-git/share/qgis/resources/data/world_map.shp", {st_mode=S_IFREG|0644, st_size=528032, ...}) = 0
openat(AT_FDCWD, "/opt/qgis-git/share/qgis/resources/data/world_map.shp", O_RDWR) = -1 EACCES (Permission denied)
</pre></p>
<p>As the file is used as source for the CRS display it does only require read access.</p>
<p>Opening it in read-only mode should get rid of the warning and be what was intended. :)</p> QGIS Application - Bug report #17779 (Feedback): Customization: no way to hide the Locator widgethttps://issues.qgis.org/issues/177792018-01-03T18:43:34ZBorys Jurgiel
<p>The Locator Widget is not listed in the QgsCustomizationDialog, as it has no objectName.</p>
<p>After setting its objectName, it's properly included to the tree, however, unticking its checbox is not effective.</p> QGIS Application - Bug report #16826 (Feedback): Range widget: ridiculously large minimum and max...https://issues.qgis.org/issues/168262017-07-10T08:38:05ZAndreas Neumann
<p>For an attribute with a Postgis data type of numeric(9.3) the range edit widgets suggests ridiculously large minimum and maximum values:</p>
<p>Min: 179769000000000006323030492138942643493033036433685336215410983289126434148906289940615299632196609445533816320312774433484859900046491141051651091672734470972759941382582304802812882753059262973637182942535982636884444611376868582636745405553206881859340916340092953230149901406738427651121855107737424232448</p>
<p>Max:<br />179769000000000006323030492138942643493033036433685336215410983289126434148906289940615299632196609445533816320312774433484859900046491141051651091672734470972759941382582304802812882753059262973637182942535982636884444611376868582636745405553206881859340916340092953230149901406738427651121855107737424232448</p>
<p>In my opinion, something more reasonable should be piced as defaults.</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 Application - Bug report #16317 (Open): Adding the same short_name option on multiple layers...https://issues.qgis.org/issues/163172017-03-08T03:49:40ZTudor Bărăscutudorbarascu@yahoo.com
<p>Adding the same short_name option on multiple layers is possible.<br />Accessing that short_name in a GetMap request results in only the first layer that was given that specific short_name to be called.<br />This could lead to confusion for big projects where by accident people use the same short_name for multiple layers.</p>
<p>How to reproduce:<br />Use the same short_name for at least two layers.<br />The GetMap request using the short_name point to the first layer that was given short_name.</p> QGIS Application - Bug report #14900 (Reopened): Styling panel: Clicking the Apply button adds a ...https://issues.qgis.org/issues/149002016-05-26T04:21:56ZHarrissou Santanna
<p>Open the map styling panel of a layer, History Tab<br />Click Apply. A new line is added although nothing has been done!</p> QGIS Plugin Site - Feature request #3986 (Open): Support for presenting index.html info about plu...https://issues.qgis.org/issues/39862011-06-14T14:52:03ZChris Crookccrook@linz.govt.nz
<p>It would be good if the repository had a feature of looking for an index.html file in the plugin zip file and providing a link to this if it exists. See</p>
<p><a class="external" href="http://www.qgis.org/wiki/Writing_Python_Plugins#Documentation">http://www.qgis.org/wiki/Writing_Python_Plugins#Documentation</a></p>
<p>Two things that make this a bit difficult are <br />1) Security - there is not control on the contents of the HTML file<br />2) References - eg references to images within the index.html file.</p>
<p>Maybe there is a better way of meeting the underlying requirement, which is to be able to provide more comprehensive information about the plugin without installing it.</p> QGIS Application - Bug report #3779 (Open): Symbols are incorrectly cropped in map canvas if rotatedhttps://issues.qgis.org/issues/37792011-04-27T02:35:03ZAlister Hood
<p>For a point layer, if I use a rectangle "simple symbol", and specify a rotation, the symbol is rotated in the map canvas, but it also has the corners cut off as if it has been cropped to fit in the area that it would have occupied if it was not rotated.</p>
<p>See attached screenshot (with a symbol dimension of 5m).</p>
<p>This problem does not seem to affect the composer, but note that it has its own bug with rotated symbols (<a class="issue tracker-1 status-5 priority-3 priority- closed" href="https://issues.qgis.org/issues/3778" title="Simple symbols rendering incorrectly in the composer and when printed (Closed)">#3778</a>).</p> QGIS Plugin Site - Feature request #23 (Open): Add an option "Create a bugtracker"https://issues.qgis.org/issues/232011-03-08T22:46:40ZPaolo Cavallinicavallini@faunalia.it
<p>On uploading a plugin, the author should be presented with the option of automatically create a bugtracker instance for it. This could be compulsory, or at least strongly recommended.</p>