Hi,
I found a bug in VBSEO that need to be fixed ASAP.
The bug is always reproducible. The steps required to reproduce the bug are the following:
- Assume that VBSEO is installed on a domain named www.somesite.com
- Populate a PHP variable with an anchor like this:
and print the variable from a VB template (edit the template to include the variable $anchor1).PHP Code:$anchor1 = <<<EOF
<a href="http://www.somesite.com/openx/www/send/unc.php?oaparams=2__bannerid=15__zoneid=3__cb=5d73316f4f__maxdest=http://www.somesite.com/rp.php"
EOF;
- The final output page (after processing by VBSEO) is this:
Where VBSEO finds the first equal sign, it inserts the string "http://www.somesite.com/", in this particular case, this is happening after the string "oaparams";HTML Code:<a href="http://www.somesite.com/openx/www/send/unc.php?oaparams=http://www.somesite.com2__bannerid=15__zoneid=3__cb=5d73316f4f__maxdest=http://www.somesite.com/rp.php"
The expected output is this:
HTML Code:<a href="http://www.somesite.com/openx/www/send/unc.php?oaparams=2__bannerid=15__zoneid=3__cb=5d73316f4f__maxdest=http://www.somesite.com/rp.php"
NOTE1:
This is happening only if the last part of the anchor contains a string that is EXACTLY as the domain name where VBSEO is installed. In other words, if you need to test this on www.yourdomain.com then replace www.somedomain.com in the anchor in both places (is appears twice).
For example, the following URL will not cause trouble:
Look at the end of the anchor and notice that it ends in "http://www.google.com/" not in "http://www.somesite.com"HTML Code:<a href="http://www.somesite.com/openx/www/send/unc.php?oaparams=http://www.somesite.com2__bannerid=15__zoneid=3__cb=5d73316f4f__maxdest=http://www.google.com/"
The above kinds of anchors are generated by OpenX. More precisely, users of OpenX will face this bug when they are creating ads to their own web site !!! This is happening only if the delivery method from OpenX is "Local mode". If they are using some other delivery options like the "Iframe" then they will not notice this bug because when an "iframe" is used, the code is not parsed by VBSEO !
Please fix this ASAP so that there will be no more issues with OpenX.
Regards,
Razvan



LinkBack URL
About LinkBacks





Reply With Quote

