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

Standalone gallery: saved with collections excluded (occasionally?) loads up blank #81

Closed
joonaspaakko opened this issue Feb 6, 2022 · 3 comments
Labels
bug Something isn't working Priority: High

Comments

@joonaspaakko
Copy link
Owner

joonaspaakko commented Feb 6, 2022

The issue seems to be that it's still looking for the collections data file and that is causing some kinda conflict. Should be pretty easy to fix.

Navigating to another page or refreshing the current page should get you around the issue.

The only proper workaround in versions 0.2.7 and 0.2.8 would be to save the gallery with collections...

@joonaspaakko joonaspaakko added the bug Something isn't working label Feb 6, 2022
@christianboyle
Copy link

Yea, I just started experiencing this.

Initially there is a JS error in console that says the collections.xxxxxx.js is 404, but I'm seeing some other missing files too.

When I initially load the standalone page it redirects to /*/library, but shows 0 books. If I then click on Library in the header or reload the page then my books show up.

If you watch the Sources panel before and after reloading the page you'll see 4 files get added:

book.js
grid-view.js
book.css
grid-view.css

2022-02-27_11-42-44AM
2022-02-27_11-43-08AM

@joonaspaakko
Copy link
Owner Author

joonaspaakko commented Feb 28, 2022

@christianboyle, I think the other files were just a chain reaction to the missing collections file (error or no error). The collection file is loaded before those files are loaded and so when it's missing, it creates a blockage preventing basically anything past that point.

It will most likely be at least a month before the next real release will come out and that is probably too generous of an estimate.

I made a build of the extension that should have this issue fixed, so if this is a big issue for you, you might as well install this build for now:

  1. Export your existing data into a JSON file.
  2. Disable the current extension (to avoid conflicts). No need to remove it, in fact it might be better to keep it.
  3. Download this build audible-library-extractor-v0.2.8-issue81-hotfix.zip
  4. Then follow these dev release installation instructions (at the very bottom — expand: read more...),
    • except in step 0 use the hotfix you downloaded above.
  5. Import the old JSON data

This build so was somewhat hastily checked, but it's the first change since the last version so assuming the pages load up, you shouldn't end up with more issues. I did check various standalone gallery configurations and it seemed to be loading just fine.

@christianboyle
Copy link

@joonaspaakko Awesome, this new hotfix build works as expected. Thanks for the quick fix!

@joonaspaakko joonaspaakko pinned this issue Sep 22, 2022
@joonaspaakko joonaspaakko unpinned this issue Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Priority: High
Projects
None yet
Development

No branches or pull requests

2 participants