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
What happens
In specific scenarios, QGIS uses old conflicted geopackage and not a new one. Therefore the user is not able to create new points in this layer. When a conflicted version of the project is downloaded from the mergin, geopackage is renamed to the conflicted one, and a new geopackage file is created. In this situation, when the user created a new point and hit the save button, the point is lost from the map canvas. The workaround is to close the project in QGIS and open it again.
The solution for this problem would be to refresh the project when a conflicted version of the project is downloaded.
How to reproduce
create a project with a point layer and open it to both mergin web and QGIS
add a point in QGIS, and hit save, but don't synchronize the project and close QGIS
from mergin web, create new version of the project by uploading updated project files from the directory on the PC
open QGIS and the project (don't synchronize yet), and add a new column in the layer
now hit synchronize, you get a conflict error ➝ this is OK
hit synchronize again and now the project should be synchronized between QGIS and mergin
try to add a new point. You should see also a newly added column in the form.
now hit the save button for the new point ➝ point disappear from the map (this is the problem)
What happens
In specific scenarios, QGIS uses old conflicted geopackage and not a new one. Therefore the user is not able to create new points in this layer. When a conflicted version of the project is downloaded from the mergin, geopackage is renamed to the conflicted one, and a new geopackage file is created. In this situation, when the user created a new point and hit the save button, the point is lost from the map canvas. The workaround is to close the project in QGIS and open it again.
The solution for this problem would be to refresh the project when a conflicted version of the project is downloaded.
How to reproduce
Author of the original task:
Jozef Budac
Original tags:
migrate to github
Original task URL: https://app.clickup.com/t/861mt43y6
The text was updated successfully, but these errors were encountered: