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

QGIS project should be refreshed when the conflicted project version is downloaded #557

Open
mergin-maps-bot opened this issue Jan 5, 2024 · 0 comments

Comments

@mergin-maps-bot
Copy link
Member

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

  1. create a project with a point layer and open it to both mergin web and QGIS
  2. add a point in QGIS, and hit save, but don't synchronize the project and close QGIS
  3. from mergin web, create new version of the project by uploading updated project files from the directory on the PC
  4. open QGIS and the project (don't synchronize yet), and add a new column in the layer
  5. now hit synchronize, you get a conflict error ➝ this is OK
  6. hit synchronize again and now the project should be synchronized between QGIS and mergin
  7. try to add a new point. You should see also a newly added column in the form.
  8. now hit the save button for the new point ➝ point disappear from the map (this is the problem)

Author of the original task:
Jozef Budac

Original tags:
migrate to github

Original task URL: https://app.clickup.com/t/861mt43y6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant