Last week I set up my fonts library in FontBase on Windows, with collections and favourites, setting the root folder on a shared drive and activating “auto-sync collections”.
Now I set up FontBase on Linux, using the same settings for the root folder and the auto-sync. I was expecting it to import my collections and favourites. Instead it seems that it overwrote it, and I lost it all.
It imported folders and fonts alright.
I don’t know what I did wrong and I didn’t do any special operation. I feel like if a FontBase-Collections.json already exists when setting a new synced root folder, FontBase should not overwrite it but read it instead, isn’t that how it works? It’s annoying to have lost this (but not too serious for now). I also don’t know if I should give up on the idea of syncing libraries between these two systems, in case I loose things again?
Hello @nclm, thank you for your post
If FontBase opens and finds an existing auto collection sync .json file, it will import it on startup, that is correct. With network drives, depending on network setup, it is sometimes possible (especially if FontBase is setup to run on system startup) that FontBase loads faster than the network drive connection is established, which may result in the app concluding that in that moment the autosync file is missing. Network drive issues are also mentioned here Frequently Asked Questions — FontBase Tutorials. With root folder located on a network drive it might be a good idea to manually export collections occasionally to keep a backup copy just in case some network issues arise
In your current situation, are the collections currently missing on both your Windows and Linux machines?
Thank you for the quick reply @nclm
Oh, I see, thank you for the clarification. So did the collections disappear for both Win and Lin OS instances?
As for guardrails - yes, you’re right, definitely
