above xml no go

edit



to this

I have successfully installed the detector mod, and tested with the latest TOR browser.

A couple of points,...

I like and prefer the red pop-up in v0.6. it isnt all in the way, but I would like it to always be on every page view. IE-giving the admin the ability to eliminate the X. (already discussed earlier so no biggie)

I noticed that the detector doesnt work on cms pages. Not a problem for me as I dont allow members to create articles, but I think the pop-up should show up there anyway.

I dont know why anyone would use the TOR system, it like slows down my browsing significantly. Maybe I am just not covert and devious enough to need it I guess.

I like it so far. Thanks!

That is strange, in the standard of coding in javascript you always needed the brackets, it was like <vb:if> and </vb:if>



That will be in the next version to eliminate a few other bugs I found. Should be up shortly.

What do you mean it doesn't work on CMS pages? It's hooked into the headers, which if I recall should be used in CMS as well. Is your style different on the CMS than the forum?

Tor runs fine with me, however I am on 50mbps optic internet so that may be why. Even some users are on a 54k internet connection, they just prefer anonymity over being public. Then you get those that are on a set vendetta to make your life a living hell, rather it be spamming your forum with useless junk, or harassing/flaming your board, getting banned, and using a new ip to do it again, regardless it is why I created it. I will actually be investing a little more time into this modification as I noticed since I started blocking Tor users that this one thorn in my side decided to use a web based proxy, which I plan to detect and stop those as well. Eventually if you make things really difficult for them, they give up haha.

InsaneMan, ignore my last code as I didnt check with both page and popup, works with one not both.

this code works for both

Hmm actually upon further investigation into the issue </vb:if> was the issue the whole time haha. I included it in the alert message which closed out the conditional before </script> could be finished. Anyway will patch this with the new version. After updating to the new version you will need to revert your tor_alert template and if using vbOptimise you will need to flush cache.

Edit: 0.6.5 released to include the persistent option and some other minor fixes.

0.6.5 download link says it is an invalid attachment.

Works for me? Try pressing f5 and download it again.

I just notice that the cms pages, most noticably, my home page, the pop-up didnt show up. I did browse around during tests and it works on all pages, but upon returning to my home page, the popup didnt enable.

I have had several instances where the cms didnt conform to vb css especially in non-oem template changes, and other attributes, but I dont know why the difference, except sometimes when using certain mods or header template changes like my custom login box in header, that cms css had to be changed also as it wouldnt follow vb forum vb css attributes. So maybe the mod is working, but the forum or additional css attributes arent applied directly to cms header changes.

Oh yes, and I use one style for all my pages.

edit to add, I am on a 50mb fibre connection too, although my remote measured thoroughput is more around 36mb. No biggie, I understand the latency involved by going thru tor.

Works great (0.6.5)

cheers