banner_jpg
Username/Email: Password:
Forums

Firefox problems

You must be registered to post!
From User
Message Body
Post #10619
user avatar
Member

4:28 am, Apr 14 2007
Posts: 8


I recently upgraded to Firefox 2.0.0.3 and the functions for adding a manga to the read list, vol, chapter, and all the other controls quit working. It works fine if I open the page in Explorer. Does anyone else have this problems?

Member

4:35 am, Apr 14 2007
Posts: 475


Fine here. Has been for a while since updating firefox.

Post #10624
user avatar
Mome Basher
Member

6:17 am, Apr 14 2007
Posts: 3380


heh, maybe its your settings? Everything is working smoothly for me >_>

________________
User Posted Image
Everyday I'm tumblin'
Post #10625
Member

6:43 am, Apr 14 2007
Posts: 2


I am having the same problems with firefox. Adding series to the lists worked just great and later (around 1 week ago) it stopped working for no apparent reason.

Post #10626
user avatar
:3
Member

6:54 am, Apr 14 2007
Posts: 74


If you have NoScript extension installed, set it to allow mangaupdates.com to run scripts.

Post #10661
user avatar


1:56 pm, Apr 14 2007
Posts: 2658


Anyone still having issues after donkabu's suggestion? I'm running 2.0.0.3 and it seems to work fine for me...

Post #10815
user avatar
Member

6:03 pm, Apr 15 2007
Posts: 8


I don't have no scripts. This is the only web site I am having problems with, works fine viewing it in IE tab. looking into security settings.


Post #11296
user avatar


10:00 pm, Apr 21 2007
Posts: 2658


Sigh sad

I don't know how to really help because it works fine for me on all browsers (Firefox 2.0.0.3, IE7...)

What happens if you click the button and wait like 10-15 seconds?

Post #12890
Member

5:22 pm, May 4 2007
Posts: 2


i have managed to fix the problem (in my firefox)... what was causing it was that there were 2 session cookies being sent in the ajax request, one for path '/' and the second for path '/ajax/', with different values.

deleting the both session cookies (in firefox) and logging in again solved the problem.

perhaps this was caused by some changes in the javascript or server side code and left some cookies in the client side (browser).

it might be a good idea to check for duplicated session cookie in list and kill them (for both paths) and force a new login just to make sure everything is ok.

Post #12902
user avatar


5:41 pm, May 4 2007
Posts: 2658


weird.. thanks for the info

You must be registered to post!