Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shapefile layer not editable after clearing Query Builder #23718

Closed
qgib opened this issue Nov 2, 2016 · 8 comments
Closed

Shapefile layer not editable after clearing Query Builder #23718

qgib opened this issue Nov 2, 2016 · 8 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@qgib
Copy link
Contributor

qgib commented Nov 2, 2016

Author Name: Steve Lowman (Steve Lowman)
Original Redmine Issue: 15798
Affected QGIS version: 2.14.8
Redmine category:unknown


In a shapefile layer, I apply a Query Builder expression. Later, I clear the Query Builder, so I can make an edit. However, the 'Toggle Editing' button is still greyed out, and the Layer Source has the full path but with ".shp|layerid=0" at the end of it. I can work around this by saving, closing, and re-opening my .qgs file. Then, the layer is back to normal and I can edit it.

@qgib
Copy link
Contributor Author

qgib commented Nov 2, 2016

Author Name: Steve Lowman (Steve Lowman)


Should have said, "..., so I can make an edit to a filtered-out feature."

@qgib
Copy link
Contributor Author

qgib commented Nov 2, 2016

Author Name: Steve Lowman (Steve Lowman)


I notice that if I change the filtered attribute value in the Query Builder, then I can edit the features thus made visible.

@qgib
Copy link
Contributor Author

qgib commented Nov 2, 2016

Author Name: Steve Lowman (Steve Lowman)


I tried changing the filter expression to LIKE '%' as an alternative to clearing the Query Builder, and that was a good work around. However, then I cleared it, and the layer was still editable. Therefore, I cannot reliably reproduce the issue, because I do not know what exactly triggers it. However, my colleague has also experienced the issue.

@qgib
Copy link
Contributor Author

qgib commented Nov 17, 2016

Author Name: Steve Lowman (Steve Lowman)


The following may be consistent and repeatable.
Apply a query builder expression to a shapefile layer.
Save and close the file.
Re-open the file. (The layer cannot be edited)
Clear the query. (The layer still cannot be edited)

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • regression was configured as 0
  • easy_fix was configured as 0

@qgib
Copy link
Contributor Author

qgib commented Sep 22, 2017

Author Name: Jürgen Fischer (@jef-n)


  • category_id was configured as Unknown

@qgib
Copy link
Contributor Author

qgib commented Jan 15, 2018

Author Name: Jakob Lanstorp (Jakob Lanstorp)


I can confirm this problem still exists in QGIS 2.18.15. For now one way to fix the problem is using the changeDatasource plugin - where the '|layerid=0' text can be removed from shapefile layer source - enabling editing of the layer again.

@qgib
Copy link
Contributor Author

qgib commented Mar 9, 2019

Author Name: Giovanni Manghi (@gioman)


End of life notice: QGIS 2.18 LTR

Source:
http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/

QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.

We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4

Most plugins have been either migrated or incorporated into the core QGIS code base.

We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.

You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.

If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.

The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.


  • resolution was changed from to end of life
  • status_id was changed from Open to Closed

@qgib qgib closed this as completed Mar 9, 2019
@qgib qgib added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

No branches or pull requests

1 participant