mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 06:06:05 +03:00
[GH-ISSUE #252] Item in folder ordering is not an actual child: {"id":128,"type":"bookmark"} #242
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#242
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 @gohrner on GitHub (Apr 3, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/252
Software versions
Steps to reproduce
Not sure - I'm just getting the following error with the new Floccus version:
Item in folder ordering is not an actual child: {"id":128,"type":"bookmark"}
That's the same error message as in Issue #213, which is supposed to be fixed, though...
@gohrner commented on GitHub (Apr 3, 2019):
@marcelklehr commented on GitHub (Apr 9, 2019):
Does the message persist across sync runs or does it only occur sporadically? The whole log would be helpful to see what's going on with that bookmark.
@gohrner commented on GitHub (Apr 10, 2019):
The message persistet for several (manual) sync attempts and always reappeared at the time when I reported the issue. Meanwhile it's "gone" however, so it somehow fixed / resolved itself after some time - no idea, why or how.
@marcelklehr commented on GitHub (Apr 17, 2019):
Closing this for now. Shout if this happens again :)
@jlbprof commented on GitHub (Apr 17, 2019):
FYI, I fixed it by clicking on the option "Merge bookmarks on next run" and
it has not come back.
On Wed, Apr 17, 2019 at 12:22 PM Marcel Klehr notifications@github.com
wrote:
@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.