mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #58] Error to sync! SOLVED #57
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#57
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ibanmda on GitHub (Mar 24, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/58
Hi!
I have installed floccus 2.0 in Firefox and Chromium. Does connect to the server (Nextcloud 13.0.1) right!
But the new bookmarks of chromium/firefox not are in the subfolder. It is empty...
What's the mistake?
Thanks
@marcelklehr commented on GitHub (Mar 24, 2018):
Hey there :)
Thank you for reporting this! Let me confirm what you did and the status of floccus at the moment:
We'll get to the bottom of this :)
@norlag commented on GitHub (Mar 26, 2018):
same problem :/
@marcelklehr commented on GitHub (Mar 26, 2018):
@norlag I'm sorry you ran into this problem. Would you perhaps be able to answer my above questions? :)
@norlag commented on GitHub (Mar 26, 2018):
yes sorry.
@marcelklehr commented on GitHub (Mar 26, 2018):
@norlag Thanks! 👍 :) Could you hover over the error status to reveal the specific error message and post it here? Was the floccus folder created somewhere in your bookmarks? (It should be called
Nextcloud (...))@norlag commented on GitHub (Mar 26, 2018):
the nextcloud folder is empty https://i.imgur.com/LFHfzYz.png
but i think its my fault https://i.imgur.com/qsrmA58.png
@marcelklehr commented on GitHub (Mar 26, 2018):
mh. If you have not changed any settings, there shouldn't be any duplicates as it just copies your bookmarks from the server, which doesn't have duplicates by design. Could you check your floccus folder?
@norlag commented on GitHub (Mar 26, 2018):
on the browser ?
@marcelklehr commented on GitHub (Mar 26, 2018):
Yep, in your bookmarks. (It should be called Nextcloud (...))
@norlag commented on GitHub (Mar 26, 2018):
the folder exists but it is empty, but i think its because i changed the folder to sync to the bookmarks toolbar.
@norlag commented on GitHub (Mar 26, 2018):
I found a way to make it work :
Options -> Reset -> Choose folder -> bookmarks toolbar
and then it works but only one time, i have to do it again to make it work
@marcelklehr commented on GitHub (Mar 26, 2018):
Is the error again mentioning existing duplicates? Is there only one duplicate pair? Does floccus create those duplicates or have they been there before? What happens if you remove a duplicate?
@norlag commented on GitHub (Mar 26, 2018):
Is the error again mentioning existing duplicates? yes
Is there only one duplicate pair? no
Does floccus create those duplicates or have they been there before? they where there before
What happens if you remove a duplicate? nothing, same problem with another bookmark
@marcelklehr commented on GitHub (Mar 26, 2018):
Are those duplicates part of your bookmark organization scheme or just mistakes? The only short-term solution I can propose right now, is going through your bookmarks and sorting out duplicates.. :/
@marcelklehr commented on GitHub (Mar 26, 2018):
@ibanmda Did you have the same issue?
@ibanmda commented on GitHub (Mar 27, 2018):
Hey there!
My problem was that the adress has not contained the symbol of "/" in the end of:
http://localhost/nextcloudSorry for the inconvenience! Solved!
Regards.
@marcelklehr commented on GitHub (Mar 27, 2018):
No problem :) Glad it works now!
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.