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

Unable to load plugin into Calibre 7.9 #26

Open
Gaylaric opened this issue Apr 24, 2024 · 3 comments
Open

Unable to load plugin into Calibre 7.9 #26

Gaylaric opened this issue Apr 24, 2024 · 3 comments

Comments

@Gaylaric
Copy link

I am unable to load the Zip plug in into Calibre 7.9. I get an error message of libby-calibre-plugin-main.zip is invalid. It does not contain a top-level_init_.py file.

@Gaylaric
Copy link
Author

Has anyone else successfully loaded this plug in?

@kurumushi
Copy link

I'm using this plugin on 7.9, but it was installed before the update

@sgmoore
Copy link

sgmoore commented Apr 26, 2024

Judging from the file name, you have downloaded the whole repo, which, although it contains everything you need, it also contains things you don't need and which calibre does not need or understand.

You are supposed to download the latest zip file from https://github.com/ping/libby-calibre-plugin/releases

If there are changes in the repo you want that have not been released then what you normally can do is :

  1. Extract everything from the libby-calibre-plugin-main.zip file.
  2. Browse to where the files have been extracted and switch into the calibre-plugin folder (so that one of the files that you can see is called __init__.py)
  3. Select all the files and folders and send them to a new zip file (the name of the resulting zip file does not matter).
  4. Use that zip file when Calibre asks you to "Load plugin from file."

This normally works, but as an English speaker, I am not sure how internalization affects this process.

If you are going to use the repo, I would suggest using https://github.com/spicefather/libby-calibre-plugin as that contains one bug fix that has affected me and a few others (see #20 or #17)

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

No branches or pull requests

3 participants