You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which are send to the strings for translation but are breaking the project if translated (fields are needed as they are for the project to work properly != translated strings)
Version de QGIS
3.34.14-Prizren
Révision du code 0cdaf6d
Version de Qt
5.15.13
Version de Python
3.12.8
Version de GDAL/OGR
3.9.3
Version de Proj
9.5.0
Version de la base de données du registre EPSG
v11.016 (2024-08-31)
Version de GEOS
3.13.0-CAPI-1.19.0
Version de SQLite
3.46.1
Version de PDAL
2.8.1
Version du client PostgreSQL
16.2
Version de SpatiaLite
5.1.0
Version de QWT
6.3.0
Version de QScintilla2
2.14.1
Version de l'OS
Windows 10 Version 2009
What is the bug or the crash?
As implemented in #7456
We face an issue with
Which are send to the strings for translation but are breaking the project if translated (fields are needed as they are for the project to work properly != translated strings)
Our specific case :
teksi/wastewater#480 (comment)
Steps to reproduce the issue
Versions
3.34 and later at least
Version de QGIS
3.34.14-Prizren
Révision du code
0cdaf6d
Version de Qt
5.15.13
Version de Python
3.12.8
Version de GDAL/OGR
3.9.3
Version de Proj
9.5.0
Version de la base de données du registre EPSG
v11.016 (2024-08-31)
Version de GEOS
3.13.0-CAPI-1.19.0
Version de SQLite
3.46.1
Version de PDAL
2.8.1
Version du client PostgreSQL
16.2
Version de SpatiaLite
5.1.0
Version de QWT
6.3.0
Version de QScintilla2
2.14.1
Version de l'OS
Windows 10 Version 2009
Extensions Python actives
DPFE
1.3.10
ordered_relation_editor
0.3.6
pg_history_viewer
2.2
pg_service_parser
0.5.0
plugin_reloader
0.17
qfieldsync
v4.12.1
qgepplugin
999.0
QgisModelBaker
v7.10.7
teksi_wastewater
2024.0.5
trackable_project_files
v1.2.2
db_manager
0.1.20
grassprovider
2.12.99
processing
2.12.99
PluginLoadTimes
4.1.2
Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: