Using force_SSL Custom Field Breaks Cufon & Footer

Hi everyone,

Further to the above, I have discovered my cufon font breaks only in FireFox not in IE or Safari.

Has anyone else experienced this problem and have any thoughts on how to overcome this issue?

The footer still breaks regardless of what it’s viewed in.
“s2member_force_ssl Yes” is messing with something and I just can’t work it out ;/

Many thanks ??

Just had a reply from WebSharks Support Center.

The reply was:
s2Member can only force SSL on URLs that are in the page’s HTML, but not URLs in other files like CSS or JS files. You’ll need to edit those yourself or ask their developer to help you solve it.

This was supposed to be a plugin anyone could get their head around and use, now I need a developer???

I wasn’t given any guidance on how to edit this myself or any documentation on how to overcome this.

Can anyone else shine a more helpful light on this issue for me please?

Thank you ??

I have S2member pro working well on my website (amishmennonitehistorians.com) with part of the website (the most recent issue of the historical bulletins) gated off so only members can access them. So that works fine.

But if someone searches through the search bar, they can break into the gated area and access exclusive bulletins. Is there a way to fix this?

Thanks for talking in plain language–I’m not very advanced in all of this and am just volunteering my services on the website.

Kevin

@amishmennonitehistorians You should really have started a new thread here. Maybe the mods will move this. In the meantime, two questions for you:

1. Is the search bar in a menu or a widget?
2. Is it important to you to have the search bar visible to users who are not logged in?

My bad on not starting a new thread.

1. So far as I understand what I am looking at, I don’t see the search bar in the menu items or as a widget. I did find it in the Lifestyle childtheme (running on Genesis framework) css coding as this:
/* Search Form
———————————————————— */

#header .searchform {
float: right;
padding: 40px 0 0;
}

#nav .searchform {
float: right;
margin: 1px 0 0;
}

.s {
background-color: #fff;
color: #509ac9;
font-family: ‘Oswald’, arial, serif;
font-size: 12px;
margin: 5px 2px 0 0;
padding: 4px 0 5px 5px;
width: 175px;
}
2. We would like to have it visible to all users, even those not logged in.

Kevin

The search bar is probably part of your theme then.

Bearing in mind your answers to my two questions, the best fix is probably to go to Restriction Options - Alternative View Protection in s2member’s back-end, and check the All box.

@NorfolkUK, could be a cross-domain issue:
https://www.cssbakery.com/2010/07/fixing-firefox-font-face-cross-domain_25.html
https://coderwall.com/p/v4uwyq
https://red-team-design.com/firefox-doesnt-allow-cross-domain-fonts-by-default/

Could be you’re not specifying the right protocol:
https://www.paulirish.com/2010/the-protocol-relative-url/
https://stackoverflow.com/questions/11704756/google-web-fonts-and-ssl-error

KTS915

Thanks so much! That fixed it and now a search won’t allow back issues of the history bulletin that are restricted to paying members to be viewed. Very helpful and clear advice, and such a simple fix once you told me what to try.

Thanks too, jumbo. Fortunately my problem wasn’t cross-domain or protocol.

Kevin

Great! Thanks for coming back here and letting us know what worked!