What is the bug or the crash?
Currently QGIS silently does nothing when a field (or the geometry) of a read-only layer is modified with the field calculator. I suggest to show a warning or disable creating/updating fields. Creating virtual fields is still allowed.
Steps to reproduce the issue
- Set vector layer as read-only
- Open field calculator
- Select field to update
- Create an expression
- OK
- Dialog is closed, but nothing else happens. No data modification, which is good because layer is set to read-only. No warning, which is bad.
Versions
| QGIS-Version | 3.40.10-Bratislava |
| QGIS-Codeversion | c98da2e682 |
| |
| Bibliotheken |
| Qt-Version | 5.15.13 |
| Python-Version | 3.12.11 |
| GDAL-Version | 3.11.3 — Eganville |
| PROJ-Version | 9.6.2 (kompiliert)
9.5.0 (laufend) |
| EPSG-Registraturdatenbankversion | v11.016 (2024-08-31) |
| GEOS-Version | 3.13.1-CAPI-1.19.2 |
| SQLite-Version | 3.50.4 |
| PDAL-Version | 2.9.0 |
| PostgreSQL-Client-Version | unknown |
| SpatiaLite-Version | 5.1.0 |
| QWT-Version | 6.3.0 |
| QScintilla2-Version | 2.14.1 |
| BS-Version | Windows 11 Version 2009 |
| |
| Aktive Python-Erweiterungen |
| Mergin | 2025.3.3 |
| db_manager | 0.1.20 |
| grassprovider | 2.12.99 |
| MetaSearch | 0.3.6 |
| processing | 2.12.99 |
Supported QGIS version
New profile
Additional context
No response
What is the bug or the crash?
Currently QGIS silently does nothing when a field (or the geometry) of a read-only layer is modified with the field calculator. I suggest to show a warning or disable creating/updating fields. Creating virtual fields is still allowed.
Steps to reproduce the issue
Versions
9.5.0 (laufend)
Supported QGIS version
New profile
Additional context
No response