HTTPS Issue

[jbstansell 0]

I'm having trouble with https today, although I might have had this problem (without knowing about it) since upgrading to 2.2.1 a couple of weeks ago (I'm now I'm up to 2.2.4). My https is showing the dreaded redline through it. Is this a Pagelines problem or do I need to look for a solution elsewhere? For what its worth, I'm using the plugin Wordpress HTTPS to force https on certain pages.

[Simon 248]

Yes the css is compiled without ssl, because as far as wp is concerned your site is non_ssl You will need to add some php to the customization plugin, if you have it installed.

[Simon 248]

[code]add_filter( 'pless_vars', 'make_ssl_vars' ); add_action( 'pl_force_ssl', '__return_true' ); function make_ssl_vars( $vars ) { $vars['plSectionsRoot'] = str_replace( 'http://', 'https://', $vars['plSectionsRoot'] ); $vars['plRoot'] = str_replace( 'http://', 'https://', $vars['plRoot'] ); return $vars; }[/code]

[jbstansell 0]

Thanks, but that didn't work for me. I copied your code and pasted it directly into the "Pagelines Customize" plugin. What do you suppose I did wrong?

[Simon 248]

Into the functions.php of the plugin? is the plugin active?

[jbstansell 0]

Color me confused. The plugin is active, and it's called: pagelines-customize/pagelines-customize.php The comments to this say: /* * * DO NOT PUT PHP IN THIS FILE!!! * * Please see file functions.php in this archive. * */ I frankly don't know what that means or where I'm supposed to look. Help?

[oplopanax 0]

Did you guys resolve this? I am having the same trouble; throughout the pagelines code there are hard coded references to http:// which cause issues in all three major browsers when you log into the site using SSL -- in IE 10 my current error is 

 

 

CSS3117: @font-face failed cross-origin request. Resource access is restricted. 

fontawesome-webfont.woff

CSS3117: @font-face failed cross-origin request. Resource access is restricted. 

fontawesome-webfont.ttf

 

 

in Chrome it is 

 

 

The page at https://www.bcsara.com/member-area/forums/ displayed insecure content from http://www.bcsara.com/wp-content/themes/pagelines/fonts/fontawesome-webfont.woff?v=3.0.1. www.bcsara.com:1

The page at https://www.bcsara.com/member-area/forums/ displayed insecure content from http://www.bcsara.com/wp-content/themes/pagelines/fonts/fontawesome-webfont.ttf?v=3.0.1. www.bcsara.com:1

The page at https://www.bcsara.com/member-area/forums/ displayed insecure content from http://www.bcsara.com/wp-content/themes/pagelines/images/[email protected].

 

There's a similar one for Mozilla.

 

I added your filter into the functions.php for the child theme rather than use the customize plugin, with some effect (far fewer of these hard http links) but these are stubborn.

[Rob 547]

Hi,

 

Did you update permalinks?

 

By any chance did you adjust the .htaccess to reflect the https?

[Simon 248]

The filter AND the action?

Is your site SSL or are you using a plugin 'hack' to get one page SSL?

 

Whats the url of your site?

[beardedavenger 158]

Nice. Worked perfectly.