mscreative9,
Most of the time when there are security error messages involved with third party
codes, I have found that they are usually related to the image reference and not to the hyperlink. In other words, in this example -
CODE
<a href="http://www.example.com/">
<img src="http://www.example.com/image.gif" />
</a>
- the issue is the IMG element and not the A element. If I were to check the domain's URL with the secure protocol and it worked -
CODE
<a href="http://www.example.com/">
<img src="httpS://www.example.com/image.gif" />
</a>
- Then this can continue to be used, even in the secure pages through checkout. If their server does not have an available secure mode, this reference won't work anyway. In this case, you will need to download the image from their server and then upload it to your own server and reference it locally -
CODE
<a href="http://www.example.com/">
<img src="/images/image.gif" />
</a>
- And this will prevent the problem.
I hope this helps.