netbouy, are you working on your site at the moment?
http://bkinky.co.nz/index.php << does not work
Wanted to have a look at your site/problem but will try again later.
netbouy, are you working on your site at the moment?
http://bkinky.co.nz/index.php << does not work
Wanted to have a look at your site/problem but will try again later.
Website Rob,
you can see the issue on a number of ZC sites with firefox.
I checked out the first 5 websites from the showcase where there is an https login and a search box on the same page and they all threw the warning...
For example, using Firefox go to the login page on this site from the showcase (should be an https connection). Instead of logging in, try submitting something in the search box... you should get the warning.
Now, if the site is online, try the same thing here ... the warning should not be displayed (hopefully).
With the MomoFresh site I did get an Warning popup but that is due to this:
https://ssl.google-analytics.com/urchin.js
Whenever you hard code an offsite link on an 'https' page, and then go to a non 'https' page, you will always get a Warning msg. One removes the off site link to remove the Warning popup.
I did not get any Warning msg. on your site so it does look like your problem is solved. Speaking of which, guess I missed the warning earlier in this thread, about your site. I don't work with those type sites myself.
hey rob,
yea net recoded all the files to fix it,
but it is a stock issue,
Zen cart PCI compliant Hosting
This particular Warning msg. is actually due to the individual Browsers themselves. Some Browsers give an option to 'Warn when loading a page with insecure items' or along those lines. Some Browsers do it automatically.
For example, Mozilla (the original not FF) allows for this:
Under options, 'SSL Warnings',
Viewing a page with an encrypted/unencrypted mix
I could not find an similar type option in FF v1.5.9, so I guess it is built in.
To my knowledge, there is no code one can use to overcome the Warning msg. -- except for making sure you are not mixing secure/insecure links on secure pages.