Bug Unsure if bug or not: Shout loading...

[cliff p]

Has anything changed from 3.8.6 vbulletin and VBshout 6.1.0, to 4.2 Vbulletin and VBshout 6.1.0?

I've noticed that the live forum I'm running has no issues with regards to the shoutbox (AT WORK), however the demo site I'm building does not show the shoutbox (AT WORK). It just continually displays "shoutbox loading". I can see the shoutbox fine from any home computer.

Would it have something to do with the javascript? Are there significant differences?

 

[Fillip H.]

If you've upgraded your vBulletin, you need to re-import the product XML file with the vBulletin 4.x version in order for it to work

 

[cliff p]

Yessir, I've done that. It's working fine from home on all browsers. It's only at the office that it doesn't work. I just find it strange since the 3.x version works fine on a 3.x forum at the office.

 

[Fillip H.]

Are you able to install the Firebug extension (or indeed even use Firefox) from your work computer?

If so, you can try that, and open the Firebug pane and see if it has any extended error information regarding the AJAX request for vBShout.

 

[cliff p]

I know I get a security dialog box that pops up in IE, and then the shoutbox displays. I don't have the issue with Chrome, because Chrome for whatever reason decides not to display notifications for issues like this. I cannot access this site from the office either as it's blocked by content filtering, categorized as "gaming".

At any rate, I'll retrieve the .js errors (think they were "undefined" errors) from work tomorrow and e-mail them to myself to post here tomorrow evening.

I've got a bunch of other bugs related to DBT mods with IE9 to sort out right now

 

[cliff p]

So it actually failed at line two of the vbshout.js script. Says something about the $ as unknown. I did take a screen capture but forgot to send it to myself

 

[Fillip H.]

Sounds like it can't fetch jQuery. Can you try to manually access the jQuery URL via your browser at work and see if it works?

 

[cliff p]

I've just started my vacation and won't return until the 2nd of January. I'll have a moment to test it at that time.

 

[cliff p]

It dawned on me that the issue was likely that jQuery was issued from Google's server.

I changed the template to pull jQuery directly from jQuery.com, and it's working fine at the office now. Thought I would provide an update. I did send an e-mail from vb.org as well.