Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] - Add an option to export and import whitelist (settings) #202

Open
BUZZARDGTA opened this issue Jan 22, 2023 · 4 comments

Comments

@BUZZARDGTA
Copy link

BUZZARDGTA commented Jan 22, 2023

Is your feature request related to a problem? Please describe.
Working on big bookmarks database, recently I had to retrograde from v4.0.0 to v3.1.0 because of v4.0.0's issue: #201.

Describe the solution you'd like
I'd like an export and import whitelist/settings button that would help me not manually whitelist every single bookmarks again.

@cadeyrn
Copy link
Owner

cadeyrn commented Jan 22, 2023

This will depend on the whitelist overhaul in #96.

I had to retrograde from v4.0.0 to v3.1.0 because of v4.0.0's issue: #201.

This doesn't make sense. Nothing changed at all between 3.1 and 4.0 in regard to the broken bookmarks check.

@BUZZARDGTA
Copy link
Author

BUZZARDGTA commented Jan 22, 2023

This doesn't make sense. Nothing changed at all between 3.1 and 4.0 in regard to the broken bookmarks check.

I sent you privately a huge bookmarks db, you should really check it out and watch by yourself how bad the results are with the "http" sheme ... #201

@cadeyrn
Copy link
Owner

cadeyrn commented Jan 23, 2023

I sent you privately a huge bookmarks db

I will do once I find the time. But again: There were not changes at all within the code to check for broken bookmarks. The things that were mentioned in the release notes were the only changes: https://github.com/cadeyrn/bookmarks-organizer/releases/tag/v4.0.0

@BUZZARDGTA
Copy link
Author

BUZZARDGTA commented Jan 23, 2023

There were not changes at all within the code to check for broken bookmarks. The things that were mentioned in the release notes were the only changes:

This makes me think that it's either Manifest V3, and you would have to change some lines of code that have changed since this new version see:
https://developer.chrome.com/docs/extensions/mv3/mv3-migration/
https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/
or a dependencies cuzing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants