Secure and non secure add to cart links

[BrownCo]

Hey Folks,

I have a miva 5 store i'm setting up and have run into a snag i could use some direction on.

All my "add one to cart" buttons pass their form params to the regular http:// address, however I have a few products that have required attributes. When a user is prompted to fill in these attributes the form that passes the attribute values is linked to the secure address of the site.

This results in an security warning if a user wants to add another product to their cart later in the session because the regular "add to cart" form is still pointing to the non-secure url. (the error is the "you are submitting a non-secure form, information passed may be visible by other parties..").

Is there a way to have the required attributes form not point to the secure url so the user doesnt actually enter the SSL layer untill they need to during the checkout process?

[Vic - WolfPaw Computers]

The problem is likely a graphic or css call in your missing attribute pages.

Do you have a URL to a product this happens with?

[d_host]

BrownCo,

Have a look at that product properties in your store admin. Chances are you hardcoded the paths to images (full and/or thumbnail) with the absolute path to your web site.

Instead of using:

http://www.YOURdomain.com/mm5/graphics/product.jpg

use this:

graphics/product.jpg

This way when you switch between non-secure and secure modes you will not get the security warning you mentioned.

[BrownCo]

Hey thanks for the quick replys guys.

I actually figured it out for myself for a change!
In the page editor i dug into the "Missing Product Attributes" template and found the MV script reference to the form path.
(&mvt:global:secure_sessionurl;). Changing that from the secure_sessionurl to sessionurl did the trick for me.

Just to clarify to the above posters as well it wasnt the dreaded "you are viewing a page with secure and non secure elements" error which definately could have been resolved by a css call or image reference mistake in the admin, but it was the "submitting a non-secure form" error, casued by a form path pointing to a non-secure url from within an SSL page.

Thanks again for the speedy followups!

[massbay]

We had the same issue, with the same solution (revising the missing attribute page). I think it became most apparent with the Firefox browser.