Data lost when copying config from one workspace to another

Hi,

I have two workspaces in SiYuan. I wanted to copy all the config from one workspace to another. I copied the "conf" folder from the first workspace folder to the second.

However, in the second workspace, all the notebooks from the first one appeared. I deleted them manually. Then, when checking the first workspace, all the notebooks were gone from it as well.

There was some important data in those notebooks, and I have no idea how to restore them. I assumed the workspace folders are completely independent one from another, so why does something so simple as copying all the config also copy all the data, and synchronizes that data between the folders?

    Welcome to here!

    Here we can learn from each other how to use SiYuan, give feedback and suggestions, and build SiYuan together.

    Signup About
    Please input reply content ...
    • zxhd86 1

      You can first disable synchronization, manually roll back the snapshot and then change the sync mode to "Full manual sync". Click on Sync in your settings menu again but this time choose "Upload local data snapshot" as a direction for synchronizing.

      After that, change back to automatic syncing.

    • MiscReply
    • 88250

      Please refer to @zxhd86 's solution above, which is to use "Full manual sync" to upload.

      image.png

    • 88250

      There are currently no plans to support the import and export of configuration files. For now, you can consider manually copying and modifying the content before pasting.

      For example, if you do not need synchronization settings (including data repo), you need to delete the "sync" and "repo" fields in the configuration file.

      1 Reply
    • akmtk
      VIP Warrior Author

      Ok, I see. How about the ability to roll back to a snapshot and sync it back to the cloud, as I was writing in my post above? Currently, the only way to do so is to remove the entire cloud folder, which also erases all the history, which is suboptimal.

      1 Reply
    • Visit all replies