mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #237] json.item is undefined #227
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#227
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 @f24nz on GitHub (Feb 26, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/237
When trying to sync bookmarks from the browser to the nextcloud I get this error and the bookmarks are not synced:
json.item is undefinedBookmarks created in the nextcloud app, can be synced without an error.
Software versions
@marcelklehr commented on GitHub (Mar 1, 2019):
Can you provide a debug log? (You can send it to me vai mail, if you like. In fact, I encourage it.)
@f24nz commented on GitHub (Mar 9, 2019):
Sorry, it was my fault. There was a problem with the domain redirection.
@marcelklehr commented on GitHub (Mar 9, 2019):
Mh, still the error message could probably be improved :D
@f24nz commented on GitHub (Mar 9, 2019):
True, I'd be glad to contribute to that. Where do I find the logfiles of floccus?
@marcelklehr commented on GitHub (Mar 9, 2019):
Ah, that won't be necessary. Those would only have been necessary if there was a bug in floccus, as it stands I think I know where things went wrong.
@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.