Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

QGIS project conflict breaks Mergin project #382

Closed
saberraz opened this issue Apr 20, 2022 · 3 comments
Closed

QGIS project conflict breaks Mergin project #382

saberraz opened this issue Apr 20, 2022 · 3 comments
Assignees
Labels
bug Something isn't working critical The most critical classification

Comments

@saberraz
Copy link
Contributor

If there is a QGIS project conflict (qgz or qgs), the plugin creates my_project_conflictV2.qgz within the same folder.
Having more than one QGIS project breaks the sync and validity of Mergin project. We need to use another naming convention for qgz/qgs files.

@saberraz saberraz changed the title QGIS project conflict messes up Mergin project QGIS project conflict breaks Mergin project Apr 20, 2022
@saberraz saberraz reopened this Apr 21, 2022
@PeterPetrik PeterPetrik added bug Something isn't working critical The most critical classification labels Apr 21, 2022
@wonder-sk
Copy link
Contributor

I would suggest that for .qgs and .qgz we have a special treatment and add ~ at the end of the filename - so it will become e.g. project (conflicted copy).qgz~ and it should not break projects anymore

@alexbruy
Copy link
Contributor

alexbruy commented May 5, 2022

Fixed in mergin client MerginMaps/python-api-client#135

@alexbruy
Copy link
Contributor

alexbruy commented May 5, 2022

Also in Input MerginMaps/mobile#2075

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working critical The most critical classification
Projects
None yet
Development

No branches or pull requests

4 participants