Note. It’s OK for your theme to use hard-coded URLs to http://
. s2Member can work around this if you specify s2member_force_ssl = yes in a Custom Field for the Posts/Pages that you place Pro Forms into. Or, you can simply link to the Post or Page with a URL that ends with ?s2-ssl=yes
https://www.crossfitulster.com/90month-recurring-loyalty-discount/?s2-ssl=yes
Here are things that s2Member does NOT have the ability to work around:
1. If you have external CSS stylesheets that use hard-coded http:// links (that’s not very common though, and I don’t find any of that on your site).
2. s2Member cannot force a particular server to support the HTTPS protocol. Your site works fine in Firefox/IE when I access secure pages with /?s2-ssl=yes on the end. However, in Google Chrome, all resources in the page must actually support the HTTPS protocol.
So the reason you’re having trouble is as follows:
1. Be sure to link to those Posts/Pages with /?s2-ssl=yes on the end. Or, supply the Custom Field s2member_force_ssl = yes for each Post/Page that contains an s2Member Pro Form. See also: http://codex.wordpress.org/Custom_Fields#Usage
2. Remove any external dependencies from your site, where the external dependencies do NOT support the HTTPS protocol. On your site, I find these resources which cannot be served over HTTPS, because the server they reside on is external from your own site, and they don’t support SSL.
https://thefoodee.com/mod/?verif=yes&mod_w=180&desc_l=100&mod_h=230&format=vert&text_size=9&bg=222222&text_color=cccccc
That’s it. Remove this dependency and you should be good.