View Full Version : Page Error


wesmorris
05-05-04, 10:18 AM
A runtime Error has occurred. Do you wish to Debug?

Line: 19
Error: 'null' is null or not an object

This happens a lot now. I haven't been paying close attention to the circumstances, as I thought it was every page load. It didn't do it when I clicked to post a thread, but when it loaded the page it did.

I'm using IE 6.

Just thought you should know about the error.

wesmorris
05-05-04, 10:19 AM
it did it for instance, as the page was loading from having posted the thread. but it doesn't do it when I go to write a post. only after the post..

it doesn't do it at the control panel either, it seems to be any time I load a thread.

wesmorris
05-05-04, 10:24 AM
okay what's weird is that on my 98 machine it doens't do that, but on XP machines, errors. funky.

Stryder
05-05-04, 11:27 AM
As I mentioned in another thread on the exact same error, it's just because a Javascript line declares a value like so:

Var something="";


I believe the errors complaining that "" isn't Boolean (TRUE or FALSE), that it's "null" and thats why the error occurs.

However it's possible to turn "Script Debugging Off" for most people that use Internet Explorer (Other than (Q) For some strange reason) which will stop the error messages appearing.

Btw, it's a fault with Microsofts parenthesis of Javascript Parsing, rather than a Javascript error. So the bugs where you can guess you usually find them.

wesmorris
05-05-04, 12:04 PM
I see, well, I disabled script debugging and it stopped bitching about it, so meh. *shrug*

Rappaccini
05-05-04, 10:09 PM
Wesmorris, do you have a cousin or relative named Ryan O'hara?

How about one that lives in Florida?

wesmorris
05-05-04, 10:19 PM
Not that I'm aware of...

Persol
05-06-04, 05:18 PM
Some of the site features may not work with scripting disabled though. For instance, can you still rank threads?

(Haven't looked at the page source)

wesmorris
05-06-04, 05:44 PM
It's script debugging that I disabled.

Persol
05-06-04, 06:11 PM
Ahhh... ummm... welll... good idea
*insert sheepish smiley face here*

mouse
05-07-04, 09:49 AM
As far as I can tell, the error occurs due to the fact that there is no element with an id="qr_quickreply".
Firefox points to this line of code as the source of the error:
fetch_object("qr_quickreply").disabled = true;
The fetch_object (by the author defined) function tries to fetch an element on the basis of the string given to it as the first parameter. But alas, in the page presented, there is no qr_quickreply element. In Internet Explorer this problem presents itself as an error claiming that "null" is not an object. In firefox the error is more clear, claiming that fetch_object("qr_quickreply") has no properties. Both browsers are right, but firefox is more helpfull by also stating the alleged object which had not the desired property (with the property being "disabled" in above line of code)

There is a qr_message element though, but I'm not sure if the author meant to fetch this one instead of "qr_quickreply" or whether "qr_quickreply" should have been generated, but by some bug wasn't.

wesmorris
05-07-04, 10:11 AM
Wesmorris, do you have a cousin or relative named Ryan O'hara?

How about one that lives in Florida?

And as I think about it, I think you asked me that when you were Redoubtable, not as if you're aren't still so, but of course I'm talking user names.

Stryder
05-07-04, 03:03 PM
Actually your Right Mouse, when I first checked it thats what I found (But I just couldn't remember why it was having the problem) thats why my example just stated it was null and not a TRUE or FALSE statement. Which means although I could remember the overall problem, I couldn't remember the overall Source of the Error.