-
Is it possible that Esplanade brakes ssl?
After changing to Esplanade while posting the ssl isn’t full. Is it because of the fonts? If so which one should I set up to have a full ssl certificate?I believe the problem is with the Google Web Fonts. In functions.php line 469, you should have this:
$web_fonts_stylesheet = 'http://fonts.googleapis.com/css?family=';
Try replacing it with:
$web_fonts_stylesheet = 'https://fonts.googleapis.com/css?family=';
If the SSL is still broken try searching in the theme files for each instance of http:// and replace it with https://. Alternatively try replacing it with a simple // to make it protocol independent.
There is no such line in functions.php (well there is a prt of it – $web_fonts_stylesheet = ‘http://fonts.googleapis.com/css?family=’; I do not see the rest of the code behind this line.
I have tried to switch to https in all places in this file with fotns.googleapis but had no luck. Also the // trick gave me no luck.Is there a way to add a font whcich wont brake the ssl? It is crucial for me.
I have chosen other fonts from the list that are not pulled from outside (I’ve checked on gtmetrix.com the elements that are loaded) but still while writing the ssl is not full. Maybe it is something else than the fonts? I have tested the site with stock twenty ten and it works ok so this is a mystery for me 😉
If you prefix the Google Web Fonts stylesheet URL with https it will send all fonts over https. It probably some other file. What is you URL?
The problem is only when I try to add a new post. Inside admin area and on front page the problem doesn’t exist.
Looks like a full SSL to me, what do you mean when adding a new post? Even single posts appear to be fine.
When editing a post inside wordpress admin center or adding a new post. That is why it is strange to me. On stock twenty ten it is ok. In firefox when going back to homepage the ssl goes back to fully secured but in chrome it indcates that it is not fully secured. For end user this doesn’t make a difference as he always sees the fully one just the writers see that the ssl isn’t full.
Hope that I make myself cleare as it is hard for me to explain it in english 😉
I made some screnschots to explain it better:
Here is with twenty ten stock theme: http://i46.tinypic.com/2exypvc.png ssl ok
Here is with esplanade: http://i50.tinypic.com/2a7dg6w.png no full sslIn firefox it goes back to fully secured after going to home page but chromium sees it as broken all the time and to see it as fully secured you have to close the browser and load it again
Also it looks like there is something like a frame (there is this white space on the right) inside the writing field- i was holding the “a” button and in firefox it was going in one line both in esplanade and in twenty ten but ich chromium it automatically started a new line: http://i50.tinypic.com/1z3ys0n.jpgI think I know now what the problem is. In editor-style.css the first line imports the Google Web Fonts stylesheet. Replace there http with https.
You must be logged in to reply to this topic.