does it work on vbulletin 4.0.x or 4.0.8 if not how can i make it work please

I don't know of anyone who has tried it on 4.0, I may try it soon.

Small xss issue fixed today, new code uploaded. If you want, all you need to fix the error is upload the new externalredirect.php

And what results? Does it work on 4.x?

This mod will not work on 4.x.

It also looks like it will kill VigLink or Skimlinks or similar services if any forums are using them. They depend on direct external links.

I ported this mode to vb4 (4.1.4).
Someday I will create a complete public package, I hope )))

P.S. Skimlinks may not work - I don't use it.
Remember that you can add some domains to white-list or create simple login in externalredirect.php to make necessary 302 redirect instead of showing second-step page..

I installed this on 3.8.4, I'm not sure if it is working or not. When I click an external link I get a white page for a moment and then it goes directly to the destination without giving the redirect message. I rebuilt the cache after the edits and installing.
in vboptions i selected yes for all the options.

Hi,

I installed this on 3.8.7. It is working fien with external links. I have added my domain in the whitelist. But still any internal links are been shown as nofollow. They are not redirected but they are nofollow.

What can be done? Please help.

Thanks.

Had to remove this because of spammer sites abusing it. They send requests to the externalredirect.php file with their own urls. Now I have a lot of unwanted traffic to my site. Many of the referrers claim to be Google bots. Just felt like posting this so others can be aware of it. Spammers take advantage of redirect scripts to boost their page rankings and to score free traffic to their sites.

Interesting. How did you discover this?

Had the same problem. I discovered it after a server change and reviewing the traffic log. MANY request went straight to the redirect file with different URLs.

I did put an htaccess rule in place to deny direct access to the file. However, for Google not getting massive 403 errors, I did put the file into robots.txt for denial too.

Still using the plugin with this configuration without any problems now.