Ye, although you might wanna make sure and wait for another person to confirm my answer as I am on the fence. Better yet, why don't you e-mail the Verisign guys because they can answer you better...
Looking at your page source, this is all I could find:.
That's a SSL killer....
Peek at this:.
Google-analytics and SSL, They don't play nice together..
Sorry, I should have given you a different URL. We do not have google analytics in the files associated with the store..
Oh but you do..
Look at the page cource for the login page:.
<! footer_eof //>..
I see!!! Wow! I don't remember adding that to the footer at all, but it has been a couple of years since the store was set up. I'll take off right away and test..
Thanks so much for you quick and kind help!..
Post again if that doesn't fix it but that's all I could find...
Ok, wait. Could this be the result of a contribution?..
I don't know of any contribs that have you add that code...
Hi. Our webhost recently made some changes which required us to reconfigure our store to use a new shared secure server. After we made the changes to our config file which we started running into problems w/pop-up security alerts. After much digging I discovered that our host was using port 80 for their shared secure server so I made the appropriate edits to the application_top.php and the alerts have ceased. Problem is the security lock icon is still not appearing at the bottom of the browser on some very key pages, including login_php and checkout_payment.php..
1. Have tested in both IE & Firefox. In IE the lock appears momentarily and then disappears. In Firefox, the lock has red mark through it..
2. The page(s) are properly at "https://...".
3. Base href is set to https.
It is my understanding that this can occur when there is mixed content on a page. I see that product images and the links on the left side of the page are pointing to http, so I'm pretty sure they are the culprit. What is the best way to solve this issue? We are using SEO url's..
Can't really do much without a URL..
Links pointing to http will.
Cause mixed content errors..
Mixed content errors are caused by scripts or images from HTTP sources on a HTTPS page...