hilaryl
04-19-2015, 11:29 PM
Hi,
Some of our IE users have just started getting this error message. I have seen it in both IE8 and IE9 (not sure about later versions).
'vBulletin' is null or not an object
It seems to happen the first time a page loads, but if you refresh the page, it doesn't happen anymore.
There are other error messages that started happening at the same time, the only difference being the variable which is 'null or not an object'. One is 'vb_XHTML_ready' and the other is 'PHP'.
The 'PHP' variable error is the one that causes the most grief because it relates to the text editor so when people try and post, they get a message saying there aren't enough characters - but there are.
I believe what ever the cause is, is the issue for all the errors though.
I have attached a screenshot showing the message.
Nothing javascript related was altered before the error messages started appearing.
I understand IE8 is outdated, so it's not supported anymore - but we do have users who still use it, so would love to get the errors fixed up.
If anyone has any suggestions or advice, would love to hear it.
Cheers,
Taylor
Some of our IE users have just started getting this error message. I have seen it in both IE8 and IE9 (not sure about later versions).
'vBulletin' is null or not an object
It seems to happen the first time a page loads, but if you refresh the page, it doesn't happen anymore.
There are other error messages that started happening at the same time, the only difference being the variable which is 'null or not an object'. One is 'vb_XHTML_ready' and the other is 'PHP'.
The 'PHP' variable error is the one that causes the most grief because it relates to the text editor so when people try and post, they get a message saying there aren't enough characters - but there are.
I believe what ever the cause is, is the issue for all the errors though.
I have attached a screenshot showing the message.
Nothing javascript related was altered before the error messages started appearing.
I understand IE8 is outdated, so it's not supported anymore - but we do have users who still use it, so would love to get the errors fixed up.
If anyone has any suggestions or advice, would love to hear it.
Cheers,
Taylor