saishy / certainmangareader Goto Github PK

Partially from old thread.

Issues:

• Compact mode occosionally slowing down browsers to a crawl.
• Chapters deleted from manga sites after you read them cause the update system to hang until manga is re-added.
• Unstable on 32-bit Firefox. Might be caused by the memory leak.

Suggestions and requests:

• Mangacow, Kissmanga and Crunchyroll support.
• Fixing Batoto's symbol bug.
• A button next to the blue arrow button to go to the next chapter
• Categories
• A permanent counter for how many series with new chapters are in the list.
• Sorting options.
• A way to sync with a MyAnimeList account

Help, I don't know how to install your addon manually in my firefox, I have downloaded the source code but I dont know what steps I have to follow :( Can you help me plz. I want to install this version 2.0.0beta2.

It doesn't work on pages and I can't even click the icon on the toolbar. Though this is on pcxFirefox (I tested it and it works on a normal Firefox), so I am not sure if you would care.

Also changing the chapter from the addons UI doesn't work to begin with, it redirects back to the same chapter.

Hey, do you have any plans for updating this extension to work with the new firefox WebExt policies?

Primarily use mangapark to read my mangas

wondering if you could add the site :D

Love the addon btw~

its not working in mangastream.com seem like they change the domain address or something like that.
please solve this problem.
thank you

Hi. Love the add-on, but there's stuff I would like for you to add if possible:

• A permanent counter for how many series with new chapters are in the list (like AllMangasReader had)
• A button next to the blue arrow button to go to the next chapter
• A way to sync with a MyAnimeList account
• Mangacow support

Firefox's page-worker is leaving a memory leak every time it is used, currently it is being tested as a new update system for batoto.

Trying to update the manga lists results in:

Vector smash protection is enabled.
[1]    29661 segmentation fault (core dumped)  firefox
[NPAPI 30007] ###!!! ABORT: Aborting on channel error.: file /build/firefox/src/firefox-45.0.2/ipc/glue/MessageChannel.cpp, line 1861

on Archlinux

It looks like there are new mangafox servers which should be added to image loading or that there are some problem, but most chapter are loading only the first 2-3 pages and then are not loading anymore.

I don't know how to diagnose the problem any further.

Also it seems like kissmanga isn't supported anymore.
On the other hand Batoto seems to be working fine, so I guess it isn't an issue with just my setup.

But maybe it's Mangafox's fault, because they are giving a lot of 500 error and other problems when you read it one page at a time, so I guess it may just be that the extension is only trying once and when confronted to an internal server error it get stuck waiting for the image, maybe ?

So, because of the new webextension and many stupid rules on the indexeddb, it's impossible to access your old data...

This mean that if you have not exported your data in the old addon and have installed a newer version of firefox, the new addon will not be able to read your database. (You can still import on the new addon from the old export output)

To circumvent this, I'm asking for some help in developing a way to extract the data from your local database, if this works you will be able to upload your old data and receive an export output from it!

So, please backup your old data if you still have it, it will be present at somewhere like:

C:\Users\YOUR_USERNAME\AppData\Roaming\Mozilla\Firefox\Profiles\YOUR_FIREFOX_PROFILE\storage\permanent

The folder should be indexeddb+++certainmangareader-at-saishy

Hi,

I've been using the plugin just for a few weeks, but I just discovered today (the hard way) that when the connection is shaky (a bad educational wi-fi network where every other site won't load because of timeouts), the plugin really really slows Firefox down. The unresponsiveness makes the whole application near not usable.

Firefox behaved normally again when I deactivated the plugin so I think it comes from here. The main difference when I activated vs. when I deactivated the plugin was the messages I got when I close Firefox (launched in terminal) :

console.error: certainmanga: 
  Message: Error: Couldn't find the worker to receive this message. The script may not be initialized yet, or may already have been unloaded.
  Stack:
    processMessage@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/deprecated/sync-worker.js:241:11
emitEventToContent@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/commonjs/sdk/deprecated/sync-worker.js:287:3
UpdateNextManga@resource://gre/modules/commonjs/toolkit/loader.js -> resource://certainmangareader-at-saishy/lib/main.js:801:3
notify@resource://gre/modules/commonjs/sdk/timers.js:40:9

I had ~50/100 copies of this block following each other when I closed Firefox (55.0.1 (64 bits)) and the module was on.

Half of the images are trying to get the image from b.mfcdn.net instead of the specified a.mfcdn.net or zmfcdn.net.Other half gets loaded correctly from z.mfcdn.net.

I am using version 1.2.10.1

Hi again! The last update perfectly fixed the reader, but brought another problem. I am no longer getting any update notifications. The chapter lists themselves seem to update(don't take my word for it though) but the entries are not turning red or notifying. I'm still on a old 800p macbook if that's useful. Pictures attached - manga that I have not finished at all are red, but updates are not.
I only use batoto, so the other reader might work fine.

Might be that the ones like the first screenshot only show that there is a new chapter because I recently opened a previous one.

Hi there,

can you add support for :

http://www.mangapanda.com/
http://www.mangachapter.me/
http://www.webtoons.com/
http://www.mangahere.co/
http://mangapark.me/
http://www.tenmanga.com/

great app.

You're probably already aware, but bato.to is changing their reader.
I thought it might be nice to have that as a open issue here for now.
At the moment it is still possible to use it with the manga already on your reading list, but that should also break once they completely remove their old urls in a day or so.
Do you have any sort of estimate of when you might fix this?
Thanks.

Peter.

I love this addon but I must disable it. It's causing Firefox to use CPU while doing nothing at all. I wouldn't be surprised if there's a memory leak in there as well. I just went through all of my addons to figure out which one was eating CPU and this is the one that was causing the issue.
I hope it'll be fixed in the future, although it looks like updates are quite slow since the Batoto loader has been broken for months on my end (skips something like pages 7 and 8 on every chapter). Version 2.3.2 by the way.

The add-on occasionally slows down the browser to a crawl. It becomes very slow to register anything, and uses a long time to complete any actions. When I eventually managed to disable the add-on the browser immediately went back to normal. This does not seem to coincide with chapter updates.
While the browser does use unusually much CPU and RAM when this happens, its still only about 30%.
Seems to happen on both OS X and Windows. Most often when opening the browser from OS X.

Is never able to get through an entire chapter before the images refuse to load.
Im assuming this is mangafox doing some kind of scraping protection.
It would be nice to be able to toggle support for specific sites so i dont have to flick the extension on and off constantly.

Hey,
Using 2.0.0-beta2 images on mangafox don't load 90% of the time.
Sometimes a refresh might work but quite often it just does not load.
I'll have a look if i can spot the issue when I have time