PDA

View Full Version : 'vBulletin' is null or not an object


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

ForceHSS
04-19-2015, 11:46 PM
<a href="http://www.bubhub.com.au/community/forums/forum.php" target="_blank">http://www.bubhub.com.au/community/forums/forum.php</a>
update to 4.2.3

hilaryl
04-19-2015, 11:51 PM
Why would we just start receiving these errors though?

ForceHSS
04-20-2015, 12:15 AM
Because IE is crap you should force members to upgrade there is a setting in the settings/options/Cookies and HTTP Header Options = Force Latest IE Mode = Yes

hilaryl
04-20-2015, 12:25 AM
Although I agree that IE is crap, the reality is that people still use it and therefore it still causes issues.

We do have that option set to 'yes' about enforcing the latest IE mode.

I'm really hoping there is a fix to this - but still can't find anything anywhere.

ForceHSS
04-20-2015, 01:04 AM
The fix would come from IE and updating IE is the only fix I know

hilaryl
04-29-2015, 11:54 PM
We are still having issue with this.

I understand IE8 is out-datted, but I don't understand why the issue just randomly started happening.

And also, why a simple refresh solves the issue most times.

Can anyone suggest any stupid fixes that can resolve this?

Our users are not tech savvy, and if they are using Internet Explorer it's because they don't know how to get an alternative, or can't update to the latest version.

If you want more info, please don't hesitate to ask.

Cheers

ForceHSS
04-29-2015, 11:59 PM
Why not make a post on your site with a download link to either the latest IE or another browser, but if you change the setting as I said above it would force their browser to open the update url for their outdated IE

hilaryl
05-01-2015, 12:29 AM
Why not make a post on your site with a download link to either the latest IE or another browser, but if you change the setting as I said above it would force their browser to open the update url for their outdated IE

We do have the option you suggested switched on, but it won't make a difference if you are running Windows XP, as you can only update to IE8 anyway.

A solution from our end to deal with IE inabilities would be ideal.

Dave
05-01-2015, 07:54 AM
Does it also happen on the default style of vBulletin?

hilaryl
05-05-2015, 02:48 AM
Hi Dave,

No it doesn't seem to be happening in the Default Theme.

It doesn't happen in the Mobile Theme either.

I guess that means I need to investigate the difference between the two.

Dave
05-05-2015, 10:31 AM
Seems like a problem in the style in that case, could be because of colliding JavaScript files/scripts.

hilaryl
05-05-2015, 09:22 PM
Seems like a problem in the style in that case, could be because of colliding JavaScript files/scripts.

Hi Dave,

After looking at the styles and actually going through and one by one deleting scripts that have always been on the page, I found one that fixed the issue.

It had always been there, but was updated by a third party without our knowledge, so we didn't know to look at it straight away.

Thanks for your default theme suggestion, I forgot I had the ability to easily change the style and compare the two.

The issue was still only limited to IE8, but it's good to know where it was coming from.

Thanks,
hilary