Errors on site

The following error appears when viewing a profile.

edit by admin : just removing error - but now noted and being investigated.

Originally posted by z00t
The following error appears when viewing a profile.

Tell us your system used, and what browser you run. This will help figure out what may be going wrong.

I've never seen this error... how did you find it? Just clicking a user name?

More details might help straighten this out.

P-

Originally posted by Phlabibit
Tell us your system used, and what browser you run. This will help figure out what may be going wrong.

I've never seen this error... how did you find it? Just clicking a user name?

More details might help straighten this out.

P-

I've just clicked on your profile and the error appears below the green graph. When I get a chance I'll test it out on Linux + firefox.

ATM the error appears on

OS :- WINDOWS XP
BROWSER :- Firefox (I never use IE6)
REPRODUCE :- IN forum click on a user, below the big green graph its there.

Originally posted by z00t
I've just clicked on your profile and the error appears below the green graph. When I get a chance I'll test it out on Linux + firefox.

ATM the error appears on

OS :- WINDOWS XP
BROWSER :- Firefox (I never use IE6)
REPRODUCE :- IN forum click on a user, below the big green graph its there.

It could be a Greasemonkey script. Try disabling Greasemonkey and seeing if it happens.

D

I don't have greasemonkey. I even tried on a fresh account on this PC with no extensions and Firefox 1.5.0.6 and the error appears. As my regular account has all extensions and stuff, that error should not appear in another account.

If you look at the coding on the script at the line suggested, perhaps that could be the cause?

EDIT: After I finished this post and I clicked on your profile, the error disappeared.

Originally posted by Ragnorak
It could be a Greasemonkey script. Try disabling Greasemonkey and seeing if it happens.

D

In fact if you search google for that error and RHP, you will see it appears a wee bit and has nothing to do with what extensions you have /don't have.

Just found the cause here, quick fix up soon.

-Russ