Should you export from Gramps (for desktops) to create the initial XML file to import into a new instance of Gramps Web ? Or does it not matter? Does syncing also work if you exported from Gramps Web to create a new Tree in Gramps (for desktops)?
In the same thread, another user asks if a Gramps Web instance can be changed from single Tree to multi-tree? (And, if so, asks about the workflow.) Or does the number of trees need to be configured from the start?
The documentation is indeed lacking and support is welcome. But while the multi-tree feature works reliably when set up correctly, it is also very much an expert feature with more manual work required compared to the default single-tree setup. So I usually opt for doing something that benefits the majority of users trying to set up a “normal” instance. It’s great that there are expert users who are successfully running multi-tree instances, and it would be great if some of those experts could help documenting their acquired knowledge.
To close this thread, what about Web Sync order of operations.
Hopefully, it does not matter.
I am guessing (from the GrampsWeb.org Sync docs) that the expected order is that a User starts the Tree in Gramps for Desktops, exports a back up, then imports into Gramps Web.
Then uses the Gramps Web Sync. (And the version of the Gramps core has to match on both instances so that the XML schema version will also match.)
But can the users of Gramps Web Sync confirm if they have successfully:
downloaded an export from Gramps Web, created a fresh tree to import into on Gramps for deskjtops. Then done edits locally that they’ve used the Gramps Web Sync addon to update the remote instance.
downloaded as above AS A NON-ADMIN and done the same. (Where there are multiple collaborators using Gramps Web Sync from different Desktops systems.
Had collaborators (using disimilar OSes) succesfully syncing Media without constantly breaking the paths.