Driving Revenue still directing links to the wrong places
jfs has discovered links that end up entirely where they're not supposed to be:
http://footprint.wwf.org.uk/
http://www.wwf.org.uk/
Clicking on them in Camino, with all JavaScript enabled, opens up a new window (instead of going to the link in the window I clicked in, despite NO new window target being specified in the HTML) to a different site entirely:
http://www.lcoffers.com/index.htm?atid=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&q=offers+deals+coupons&askw=offers+deals+coupons
Where the atid is 011076001001006000000000005009, for anybody who wants to keep track.
This is probably due to the affiliate linking script, as it only happens when I have the script enabled; if so, it means that Driving Revenue's new implementation still has problems making links only go to their appropriate sites, except this time because the redirection is entirely dependent on their outboundlink.me server's response instead of defined in the code, no debugging can be done on the script itself to determine what links will go where. It could be another case of whack-a-mole, just like with malware on ads, except this time even paid journals can't escape it.
ETA: marta has informed me that our hard working ops team has disabled Driving Revenue at this time!
ETA the second: Back now, for the curious.
Use these to test:
http://footprint.wwf.org.uk/
http://www.wwf.org.uk/
Regular amazon link: http://www.amazon.com/Apple-touch-Generation-NEWEST-MODEL/dp/B001FA1O18/
http://footprint.wwf.org.uk/
http://www.wwf.org.uk/
Clicking on them in Camino, with all JavaScript enabled, opens up a new window (instead of going to the link in the window I clicked in, despite NO new window target being specified in the HTML) to a different site entirely:
http://www.lcoffers.com/index.htm?atid=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&q=offers+deals+coupons&askw=offers+deals+coupons
Where the atid is 011076001001006000000000005009, for anybody who wants to keep track.
This is probably due to the affiliate linking script, as it only happens when I have the script enabled; if so, it means that Driving Revenue's new implementation still has problems making links only go to their appropriate sites, except this time because the redirection is entirely dependent on their outboundlink.me server's response instead of defined in the code, no debugging can be done on the script itself to determine what links will go where. It could be another case of whack-a-mole, just like with malware on ads, except this time even paid journals can't escape it.
ETA: marta has informed me that our hard working ops team has disabled Driving Revenue at this time!
ETA the second: Back now, for the curious.
Use these to test:
http://footprint.wwf.org.uk/
http://www.wwf.org.uk/
Regular amazon link: http://www.amazon.com/Apple-touch-Generation-NEWEST-MODEL/dp/B001FA1O18/