mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #114] Newly created bookmark disappears on sync #111
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#111
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 @1stone on GitHub (May 31, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/114
Software versions
Steps to reproduce
Prerequisites:
Steps:
Expected outcome
I expected the new bookmark to be synced to the server.
Actual outcome
The bookmark was deleted in Chrome as soon as the sync was performed.
Additional notes
@marcelklehr commented on GitHub (May 31, 2018):
Mmmh. Strange. Does the particular URL redirect you when you open it?
Could you replay the above steps and provide a log of what happens in floccus?
Chrome
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "Sync nowfor the associated account@1stone commented on GitHub (Jun 2, 2018):
Yes and no.
Yes: It returns a 302 if you don't have an authenticated session (Cookie), resulting a a multi-level redirect (SAML-Authentication)
No: When testing this, there was an authenticated session, so every request was straight responded with 200.
Well, I followed your instructions (thanks for explaining this thoroughly), but unfortunately, today the problem is not reproducable anymore :-(
The bookmark which silently failed previously, no saves properly.
I've no clue was changed in the meanwhile (besides other browsers syncing).
So given that, there is probably not enough meat left to hunt this problem down.
Go ahead and close the issue if you like. I'll reopen/comment on it, in case I have the chance to analyze this again.
@marcelklehr commented on GitHub (Jun 2, 2018):
The bookmarks app also tries to access the urls you store in order to obtain meta data. When it is being redirected, it usually corrects the URL you're storing to the one it got redirected to, so that's why I'm asking.
It could be that this only happens/ed when the sync kicked in automatically on changes in the tree, or the recent release also inadvertently fixed this issue. :)
Feel free to get back to me if this should reoccur.
@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.