Portal Software - vBISpy module - live AJAX feed of new threads - for vBAdvanced CMPS

This is my first module for vBAdvanced, but its a simple one, so I don't expect any installation problems.

You can see an example of this working on:

ViperAlley.Com

You must already have a working copy of the vBIspy client v1.0.7 or better in place. (vB 3.5 users need v1.06 or better)

INSTALLATION

Add the vbispyblock.module to your vBAdvance portal - keep in mind the size of the block when you choose it's placement - if you use three columns, then really only the center column will work.

To install you should have a working copy of the VBIspy client already working on your system. Once you have one of the clients working adding vBIspy blocks to other pages becomes easier.

################################################## ################################
################################################## ################################

STEP 1

Because vBAdvanced CMPM usually resides outside of the forum directory, you will need to make one change to the clientscript/va_spy.js script that comes with vBIspy.

In va_spy.js, find:

var vburl = '';

and change this to read:

var vburl = '/forum/';

using the name of the directory your forums are in in place of "forum". This is important as otherwise the links from the vBIspy block will not resolve to the forum directory.

################################################## ################################
################################################## ################################

STEP 2

You will need to modify the 'adv_portal' template to add a few lines:

################################################## ################################

Find:

$headinclude

Add after:

<script language="javascript" src="{$vbulletin->options['bburl']}/clientscript/va_prototype.js"></script>
<script language="javascript" src="{$vbulletin->options['bburl']}/clientscript/va_effects.js"></script>
<script language="javascript" src="{$vbulletin->options['bburl']}/clientscript/va_spy.js"></script>
<script language="javascript">
    spymax = 10;
    highestid = 0;
</script>

################################################## ################################

Find:

$footer

Add after:

<script language="javascript">
    spyinit();
</script>

################################################## ################################

You are done. Activate the module and you should start seeing a live feed of threads on your portal page.

If you do not see an updating list of threads:

1) Double check that your vBIspy.php script is working properly!
2) Make sure you followed the above instructions.
3) If all else fails, open the JavaScript Console in Firefox and see what errors you might be getting.

1.0.1 - 9.28.06
Modified template for module to support 1.0.12 release of vBIspy (you can modify your template manually from this post; but you also need to note the changes to the spymax and addition of the highestid variable to be changed in your adv_portal template).

[Spikeman]

Originally Posted by osmanungur

says
The file you have uploaded is not a valid module file.

Use the module file from post #91

[Jaxx]

A user pointed out to me tonight that since I've upgraded to the new vB, vBA, and vBGallery, that the hybrid and threaded view options show this:



I was also having issue's with the AJAX quick edit. Clicking save would save the post, but you would just sit there unless you refreshed.

I found the issue to be something with the block hack.

After putting in the lines of code into the adv_portal page, this would happen. If I take it out, it works just fine.

Running vb3.6.2 and vba 2.2.1

[MPDev]

What does that have to do with this mod?

[Jaxx]

Exactly as I posted there.

I'm not sure why its doing it. But I started with a fresh style, no hacks in it at all. While installing each one by itself, things worked fine, then I got to this block hack.

As soon as I put

<script language="javascript" src="{$vbulletin->options['bburl']}/clientscript/va_prototype.js"></script>
<script language="javascript" src="{$vbulletin->options['bburl']}/clientscript/va_effects.js"></script>
<script language="javascript" src="{$vbulletin->options['bburl']}/clientscript/va_spy.js"></script>
<script language="javascript">
    spymax = 10;
    highestid = 0;
</script>

in after the $headinclude statement, I would get the above posted issues.

[MPDev]

But what relation is the adv_portal page to your other pages? It's not loaded on every page (is it?), so not sure why it would interfere with say, a thread display page.

[Spikeman]

Originally Posted by MPDev

But what relation is the adv_portal page to your other pages? It's not loaded on every page (is it?), so not sure why it would interfere with say, a thread display page.

He has the forum wrapped in vBa so it is causing errors when the thread viewing mode is anything but linear mode. Same happens on my board although I did not notice as I have threaded and hybrid modes disabled.

[MPDev]

Ah, my bad; I really don't know vBa that well. I'm not sure what to suggest.

[Trana]

Am I the only person that can't get this to work in CMPS? My vaispy page works fine. The module has been imported and shows up, but never displays any content. I have tried several different settings for my vburl but have never seen this module work at all.

Does anyone have any ideas what I can check? I would really like to get this to work.

Thanks!

[kompakt]

Originally Posted by Trana

Am I the only person that can't get this to work in CMPS? My vaispy page works fine. The module has been imported and shows up, but never displays any content. I have tried several different settings for my vburl but have never seen this module work at all.

Does anyone have any ideas what I can check? I would really like to get this to work.

Thanks!

I had that problem too. The .module works a little different in vba 2.2. After uploading your module. Create a new module manually and make it identical to the other module. Once you get it working you can delete the old one.

[Trana]

Originally Posted by kompakt

I had that problem too. The .module works a little different in vba 2.2. After uploading your module. Create a new module manually and make it identical to the other module. Once you get it working you can delete the old one.

I'm not sure what you are suggesting. What will creating a new module with the same config do? I will just have two modules that don't work.