Fails to sync existing Firefox bookmarks to new nextcloud config

Describe the bug Firefox add-on fails to sync existing bookmarks to a new nextcloud instance. I have copied my existing ‘Bookmarks Toolbar’ and ‘Other bookmarks’ folders into my new ‘nextcloud <xyz>’ folder, but Floccus refuses to sync these to the server (and no show up from the web interface). Debug log supplied which seems to indicate a problem with a parent hash?

To Reproduce Steps to reproduce the behaviour:

1. Open floccus, configure new Nextcloud account, Save
2. Open Bookmarks manager/Library, click and drag to copy ‘Bookmarks Toolbar’ and ‘Other Bookmarks’ as children of ‘Nextcloud Bookmarks’ folder
3. Attempt to ‘Sync’
4. Nothing happens.
5. Open debug log - see error

Expected behaviour Existing bookmarks folders are replicated to the Nextcloud server, and are visible in the web interface as children of a new parent folder pertaining to this computer/setup.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Gentoo Linux
• Firefox 68.2.0esr (64-bit)
• Floccus version: 4.1.0
• Floccus sync method: NextCloud webdav

Server (please complete the following information):

• OS: Hetzner StorageShare
• Nextcloud version: 18.0.4
• Bookmarks app version: 3.0.13

Debug log Issue541-floccus-4.1.0-2020-05-31

• [ X ] Debug log provided

[mjeveritt]

Yeah, I’ve been thinking about this myself. I tend to feel like people should opt-in to which bookmarks they are syncing, as syncing can be potentially destructive if you don’t know what you’re doing, and/or don’t have backups. I’ll think about how best to handle this in the new UI.

Oh yeah, been bitten by that problem since I first started syncing devices years ago, so I get ya point.

Just to check, how do I specify the root ‘All Bookmarks’ folder … does that just pop up in the selection box of the config dialogue … Found it all, and it looks all perfect now:

[marcelklehr]

Aha, you do need absolute/relative paths for the situation you describe in the Options where you are doing the Reverse of what I am doing … per-computer subfolders of a ‘master’ repository.

mmmh, no. I think you were right the first time. The new UI has validation for these things 😉

If you’d like to give it a go and provide some feedback see #531 😃