Widescreen Gaming Forum

Anyone else have problems logging into the site using the latest Firefox?

Every time I try to enter my name and password, the screen just refreshes asking for the information again. :evil:

Driving me nuts as I have to use IE7 to log in.

Thanks,

Wazoo

_________________
Gigabyte GTX 980 - SLI

i7-4770k @4ghz

16GB Ram

Planar SA2311W 3D Vision monitors (x3)

Windows 7 x64 Ultimate SP1

Wierd, using FF2 and FF3 with no problems. did you update all your add-ons? Can you try and disable them and then try it again.

Only running 3 add-ons (all up-to-date) and even after disabling them, same problem.

Don't have trouble logging into any other site so I'm stumped. :shock:

_________________
Gigabyte GTX 980 - SLI

i7-4770k @4ghz

16GB Ram

Planar SA2311W 3D Vision monitors (x3)

Windows 7 x64 Ultimate SP1

Can you try clear the cache, and tried to load the page with shift-mousebutton.

Trying to replicate your issue... only way I can do it is to disable cookies... :?

Clearing cache did not work.... and I checked and I already have Accept All 3rd party cookies checked.

Strange stuff.... I doubt the fact that I am running Vista 64 makes a difference.... but I'll try it on my Vista 32 system and see if it is the same.

_________________
Gigabyte GTX 980 - SLI

i7-4770k @4ghz

16GB Ram

Planar SA2311W 3D Vision monitors (x3)

Windows 7 x64 Ultimate SP1

My Vista 64 rig never had issues logging in to the site. Although that system still uses FF2.

I've had an issue from time to time with Safari (but I'm on here a lot). Make sure that when you login there is no "sid....." in the URL.

There is no "sid" in the url when the login page appears.... but after I enter my info and the jumps to the main forum index, there is an sid= with a huge Hexadecimal (I think) line of code after it.

Wazoo

_________________
Gigabyte GTX 980 - SLI

i7-4770k @4ghz

16GB Ram

Planar SA2311W 3D Vision monitors (x3)

Windows 7 x64 Ultimate SP1

I'm having the exact same issue as wazoo. In fact, I'm kinda glad because I was worried I was the only one. :)

For me, this didn't start until Firefox updated itself to version 3.06, which happened just a couple of days ago. Before that it was working just fine.