Bug report #17111
Trouble with value maps in any shapefile in QGIS 2.18
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Vectors | ||
| Affected QGIS version: | 2.18.12 | Regression?: | No |
| Operating System: | windows 7 ultimate x64 | Easy fix?: | No |
| Pull Request or Patch supplied: | No | Resolution: | invalid |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 25010 |
Description
Hello,
I've saved a project with with a layer on which it was active a query using the layer properties query builder.
Well, when I reopened the projects, the layer with the query appear no longer editable.
On the same layer I also used 4
'value map ' to enter the values in the fields.
Well, Even the previously setted 'values map' are not loaded on layer at project reopening.
History
#1
Updated by Giovanni Manghi about 7 years ago
- Subject changed from Trouble with query builder and values map in any shapefile in Qgis 2.18 to Trouble with value maps in any shapefile in QGIS 2.18
- Category changed from GUI to Vectors
- Status changed from Open to Feedback
- Priority changed from High to Normal
- Regression? changed from Yes to No
Hi Antonio,
one issue one ticket please.
Anyway the first in not an issue, some datasources are not editable when a filter is applied.
About the second issue do you have any evidence is a regressions (it was ok on a previous QGIS release?).
Please add the data and detailed steps on how replicate.
thanks.
#2
Updated by Antonio Viscomi about 7 years ago
Hi Giovanni,
The data are not necessary because of the first 'issue' appens with all the shapefiles I've tried, then:
A user is able to edit a subset's database before saving the project but not after that.
Then the problem, in my opinion, is in saving project with a query on a shapefile
#3
Updated by Antonio Viscomi about 7 years ago
Sorry For the second issue,
but I thought it was connected to the first one because in a project saved with the same shapefile 'not queried' vaulemap works fine.
#4
Updated by Antonio Viscomi about 7 years ago
Antonio Viscomi wrote:
Hi Giovanni,
The data are not necessary because of the first 'issue' appens with all the shapefiles I've tried, then:
A user is able to edit a subset's database before saving the project but not after that.
Then the problem, in my opinion, is in saving project with a query on a shapefile
Furthermore the shapefile remains not editable even I clean the previously saved query...
#5
Updated by Giovanni Manghi about 7 years ago
I see the problem with filtering editing, but I don't see (or understand) the problem with the value maps.
Can you add steps to replicate the issue? Thanks.
#6
Updated by Antonio Viscomi about 7 years ago
Sorry,
The problem with valuemap is not existent, I initially thought the cause of the problem with the filter was valuemap but evidently I was wrong about this.
#7
Updated by Antonio Viscomi about 7 years ago
Giovanni Manghi wrote:
I see the problem with filtering editing, but I don't see (or understand) the problem with the value maps.
Can you add steps to replicate the issue?
Sorry,
The problem with valuemap is not existent, I initially thought the cause of the problem with the filter was valuemap but evidently I was wrong about this.
#8
Updated by Giovanni Manghi about 7 years ago
- Status changed from Feedback to Closed
- Resolution set to invalid
The problem with valuemap is not existent, I initially thought the cause of the problem with the filter was valuemap but evidently I was wrong about this.
for the other issue see #17124
#9
Updated by Antonio Viscomi about 7 years ago
Giovanni Manghi wrote:
The problem with valuemap is not existent, I initially thought the cause of the problem with the filter was valuemap but evidently I was wrong about this.
for the other issue see #17124
many thanks Giovanni
and sorry for the misunderstanding I have created with valuemap