It looks fine to me in Chrome and Firefox on Mac. Here are some screenshots:
I also had a look at all 37 requests and they're all https:// request. Are you seeing this in some weird Chrome version? Have you tried updating to the latest one? Also, try clearing your cache.
BTW, PayPal express orders will not be created in BC. Customers will be sent to PayPal and the funds will be collected, but BC will not know about them.
One Chrome build had a false positive bug showing errors even when there were none under HTTPS. Other issues come from some Chrome Plugins.
Please watch his 3 min Screenr video demonstrating a concern I have = http://www.screenr.com/qzx8. Bascially, if a vistor goes to the Support section of the website then wonders of to another section like the Media pages for example, then back to the Support pages.. Chrome shows an SSL warning. Must I make all links secure? What is the best coding practice to avoid this issue?
@Liam: I disabled all my plugins but still get the SSL error if I visit http pages then go back to the https donation page. Thanks for the original tip but if you have any further tips please share.
1 person found this helpful
I tested this in other browsers and none of them have this problem. It seems to be Google Chrome issue. I did some digging around and came across this http://zach.be/2011/11/chrome-https-issue/
What you'll need to do is replicate that template and in the new template set all the paths to absolute http://wildlifewaystation.org/ pathes, then wrap the secure pages into that template. Browsers shouldn't complain about the http:// hrefs. They only throw that error is there is a GET request going to a non-secure resource.