Data lost when copying config from one workspace to another


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 ...
    • 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
    • MiscReply
    • akmtk
      VIP Warrior Author

      Update: I was able to restore the data via Main Menu / Data History, there select Snapshots, rollback to the previous snapshot.

      BUT, now cloud sync doesn't work! Whenever I sync, it gives me back the state with the deleted data. How do I force the cloud to make the rolled back state as the current, most recent?

    • 88250

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


    • 88250

      The configuration file contains cloud sync directory information, so if two workspaces use the same configuration file, they are equivalent to being connected to the same cloud directory, so they will affect each other through data synchronization.

      1 Reply
    • Visit all replies