All Mangas Reader

Hi,

in the options, when displaying the "Supported web sites" list, if you try to click on the "discuss" icon for any web site, the url were you are forwarded is the dns alias of the real server and not the dns alias of the community.

For example, if trying to "discuss" batoto implementation, you get:
https://ssl10.ovh.net/~allmanga/communi ... ome&id=332

And should get:
http://community.allmangasreader.com/co ... ome&id=332

The problem is that when on ssl10.ovh.net/~allmanga, it redirects to the login.php page... but even if you log in correctly, it then redirect to the front page of the forum... not the comment page for the supported web site intended...

That's all... not a big problem but well... correct it when you'll have time

Thank you!

Mmm... I noticed this way back, but there was no other option (unless we replace https://ssl10.ovh.net/~allmanga/community with http://community.allmangasreader.com) because we use the url from the imported mirror list (somewhere around here https://github.com/AllMangasReader-dev/ ... ns.js#L259). So, last time I meddled with that code (trying to improve it) things broke badly, so it has a "black magic" label for now, for me. If you want you can report an issue to our GitHub repository, since its easier to track problems there.

_________________
Know about me

Ok,

just to try, I added a new var amrc_alias and change the line... seems to work fine... didn't see any strange behavior.

https://github.com/AllMangasReader-dev/ ... try.js#L20
new line:
var amrc_alias = "https://community.allmangasreader.com/";

https://github.com/AllMangasReader-dev/ ... ns.js#L366
Replace var amrc_root by amrc_alias
openTab(amrc_alias + "comments.php?type=1&from=home&id=" + $(this).closest("td").data("idext"));

And I saw that the alias dns is hardcoded in a lot of place (except the one I reported):
grep community.allmangasreader js/*
lab.js: notif.url = "http://community.allmangasreader.com/comments.php?type=1&id=" + wsData.idext;
mgEntry.js:var amrc_alias = "https://community.allmangasreader.com/";
mgEntry.js: notif.url = "http://community.allmangasreader.com/comments.php?type=1&id=" + wsData.idext;
options.js: chrome.runtime.sendMessage({action: 'opentab', url: 'http://community.allmangasreader.com/'}, function () {});
popup.js: openTab("http://community.allmangasreader.com/");

Maybe we can use the new var for these too? What sort of things broke for you last time?

_________________
Know about me

Replaced the variable in commit 97f2ebab5a. Check it out.

https://github.com/AllMangasReader-dev/ ... 0a12788bf5

_________________
Know about me

Guys,
can you help me out...
My AMR just don´t show the supported web sites anymore... where what shows on the debug

Failed to load resource: net::ERR_CONNECTION_TIMED_OUT https://ssl10.ovh.net/~allmanga/communi ... sites.json
Next time to refresh chapters list : 1584594 background.js:325
Next time to refresh manga list : 86184599 background.js:339
Next time to refresh websites : 86184601 background.js:353
2Failed to load resource: net::ERR_CONNECTION_TIMED_OUT https://ssl10.ovh.net/~allmanga/communi ... sites.json
Uncaught Error: Attempting to use a disconnected port object extensions::messaging:73


The last one keeps repeating...

what can i do to make it work again?

I'm not sure if it's the same thing here or not, but I tried to go to the community website (http://community.allmangasreader.com/) and it isn't loading and is saying that it's down for me.

I've tried uninstalling and reinstalling chrome several times and I'm getting no supported websites listed. This happened a few months ago, as well, but I don't know how it was fixed (if it was even on MY end, heh). If I deactivate it and reactivate it again it stops showing my manga list at all, too...though I don't know if that's just because it can't find the websites so it's glitching out altogether, or what.

"Downforeveryoneorjustme" says the community site is up, though...so I'm not sure what's going on. Maybe I need to reinstall Chrome...again.

...I guess I can go try that, later, though I don't think I did that last time when it was fixed (don't know if I did anything or if it fixed itself).

Hey, don't bother re-installing chrome at the moment, as that won't change anything. Currently, from what I can gather, it is actually a bug for the time being and will probably be fixed soon. I tried it on a laptop I had before, and it was the same problem I am getting on my current... Which is how I can gather that it is not on my end, so if you're experiencing the same, don't worry, not your fault. The awesome developer will fix it soon! Just be patient and wait for the fix my friends.

_________________
Know about me