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

Chrome Extension : Interrupt downloads option automatically turns off on every boot #30

Open
mashrufehsan opened this issue Dec 22, 2019 · 7 comments

Comments

@mashrufehsan
Copy link

System Details:

  • Operating System: Windows 10 x64
  • Persepolis Version: 3.2.0
  • How do you install Persepolis? - Searched a lot on the internet to find a better alternative for IDM.

Issue Description and steps to reproduce:

  • "Interrupt downloads" option automatically turns off on every boot in the "Chrome extension". So every time after boot need to click on the extension and then turn the "Interrupt downloads" on to catch the download links and through it to the dm. It would be great if it can save the preferences that I change.

  • And sometimes when I attempt to turn it on, it says "Fatal error detected - Failed to execute script Persepolis Download Manager". I'm attaching the screenshot in the comment.

@mashrufehsan
Copy link
Author

image

@mashrufehsan
Copy link
Author

image

@alireza-amirsamimi alireza-amirsamimi transferred this issue from persepolisdm/persepolis Dec 30, 2019
@Antxl
Copy link

Antxl commented Mar 30, 2020

It seems to be caused by the extension failing to connect to the persepolis. Maybe the file name doesn't match or whatever.
So I just annotated the corresponding part of the code like this...
image<SendInitMessage()>
Now it won't turn off on startup, and the browser launches much faster than before XD...

@Antxl
Copy link

Antxl commented Mar 30, 2020

emmm...I forgot to say it lays in "background.js"...

@JafarAkhondali
Copy link
Member

@Antxl Which operation system are you using?

@Antxl
Copy link

Antxl commented Mar 30, 2020 via email

@JafarAkhondali
Copy link
Member

We got a known bug in windows that is the cause of this exception ...

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