mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #970] Update causes account to be wiped - unable to import json file #629
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#629
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 @dsiminiuk on GitHub (Sep 27, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/970
Describe the bug
Updating from 4.8.0 to 4.8.1 via developer console drag and drop of the CRX file wipes out the config.
To Reproduce
Open browser
Export account from floccus 4.8.0 to .json
CTRL+SHIFT+E to open plugins page
Enable Developer mode
Drag the new .crx package into the window
The account is removed.
Importing the .json file does not restore the settings.
Importing the .json file multiple times lists additional instances of the same account but none work.
Expected behavior
Existing account should remain
Importing previous config from .json should work if needed
Screenshots
@dsiminiuk commented on GitHub (Sep 27, 2021):
I had to remove the extension completely to get rid of the extra accounts, installed 4.8.0 and all is good again. Imported the .json as well without a hitch.
@marcelklehr commented on GitHub (Sep 27, 2021):
Did you set a password for floccus?
@dsiminiuk commented on GitHub (Sep 27, 2021):
@marcelklehr I don't understand.
The username and password for user auth on the server is in the .json.
After importing the .json the details of the account shouldn't the account appear in the plugin when you left click on the icon?
The only thing that was displayed was "New Account" (none of the three listed above).
Am I missing something?
@marcelklehr commented on GitHub (Sep 27, 2021):
I cannot reproduce this with Chromium 93.0.4577.82
What does this mean? They don't sync? What are the (redacted) contents of the exported json file?
@marcelklehr commented on GitHub (Sep 27, 2021):
It's possible to secure your credentials by setting a password for the whole extension, but I'm guessing from your reaction that you didn't do that.
@dsiminiuk commented on GitHub (Sep 27, 2021):
@dsiminiuk commented on GitHub (Sep 27, 2021):
Oh, I see, the "Set a pass phrase for floccus" option. No, not using that.
@marcelklehr commented on GitHub (Sep 27, 2021):
Can you clarify what you mean by not working here?
@dsiminiuk commented on GitHub (Sep 27, 2021):
In the image above you see 3 accounts that can be exported.
They are all the same account having imported the same .json three times, so it appears there is an account provisioned.
However, clicking on the plugin's icon exposes "New Account" like none are not there.
@marcelklehr commented on GitHub (Sep 27, 2021):
Mh, let's see if there are errors in the log:
Chrome
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "@dsiminiuk commented on GitHub (Sep 27, 2021):
@marcelklehr Hahaha, you may as well ask me to give you a suitcase full of cash LOL
I got to the DevTools window but I have no idea where the logs are in that mess.
Let me try an update on a different machine (5 Windows, 1 Linux Mint using this plugin) and see if I can reproduce it. If not then I'll assume I had a problem in this particular browser.
I'll do it today.
@dsiminiuk commented on GitHub (Sep 27, 2021):
@marcelklehr
I was able to reproduce this on the same version of Vivaldi (4.2.2406.48) on a different machine.
I will PM you a link to the video capture.
@dsiminiuk commented on GitHub (Sep 27, 2021):
The screen capture was so small I just attached it to an email at the address on your profile.
@dsiminiuk commented on GitHub (Sep 27, 2021):
I removed the 4.8.1 plugin (not allowed to downgrade) and installed 4.8.0 and imported the .json and all that works perfectly and as expected.
@marcelklehr commented on GitHub (Sep 27, 2021):
Can't reproduce with Vivaldi 4.1.2369.21
The screen capture indicates a bug in the overview panel, rather than the accounts being gone. Let me try to guide you through the process to get to the logs.
@marcelklehr commented on GitHub (Sep 28, 2021):
Please try v4.8.2
@dsiminiuk commented on GitHub (Sep 28, 2021):
@marcelklehr Thank you for the tutorial, I'll keep that email for later.
Also, thank you for v4.8.2, Upgrading was perfect. No loss of config.
@github-actions[bot] commented on GitHub (Mar 20, 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.