SSL Shows CSS Errors

[seoskyrocket]

I use custom CSS to extend the width of the site title area to allow the full name of our church to display on one line and it looks great on all of my pages except the following three pages that utilize SSL:

https://www.sylvaniachurch.com/apply/

https://www.sylvaniachurch.com/events/waiver-medical-release/

https://www.sylvaniachurch.com/contact/

The Chrome developer tools shows the following error:

Mixed Content: The page at 'https://www.sylvaniachurch.com/apply/' was loaded over HTTPS, but requested an insecure stylesheet 'http://www.sylvaniachurch.com/?sccss=1'. This request has been blocked; the content must be served over HTTPS.

Is there a way to fix that, and to do so in a way that doesn't get lost with future theme updates? Thank you in advance for your help!

https://www.sylvaniachurch.com/apply/

[David Chu]

Hi,
Is that you, Chad? 😉 That is really strange - it looks as though you're requesting that URL fine with https in the URL. I have 2 theories - I did notice that you're command below should really have a semi-colon after it. (I added it to the code below). I wonder if it will stop the error if you fix that.

.title-area {
  width:350px;
}

It may not, though. It's possible that having the URL looking like a GET variable will bollix something. In which case you could add that command to your regular style.css file, and that would clean things right up.

Cheers! Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[seoskyrocket]

My friend, Dave Chu! It's good to hear from you, sir! And thanks for your help! I added the semicolon, but the issues continues. How would I try the second thought you had? If it's best to hire the infamous Dave Chu again, then I'm game for that. 😉 If that's the best route, then I'd also be curious to get your thoughts on why the http://www.sylvaniachurch.com homepage scores a whopping zero on Pingdom for "minimize request size." Talk to soon.

[David Chu]

Hey Chad!
Ah, but the title is now working on one line! Oh, it looks like you turned SSL off. 🙂

If you wanted to move the code, you would go to Appearance..... Edit. That will take you into the style.css file. Then you could put that bit of code in there. Just be sure you have that code separate from other lines, and not inside comments.

/***
 this is a comment example.
***/

Or just leave it be, to me, it doesn't look very serious, frankly, but maybe you're getting dinged in Google analytics or something.

About the pingdom... I just ran it myself. I clicked the little details arrow all the way to the right of the minimum request line. It's slightly whining about two very long URL's, one for fonts, and the other for Google Analytics. Gosh, that's pretty minor. Personally, with the stellar other scores, I'd just relax and celebrate!

Cheers, Dave

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[seoskyrocket]

I only have SSL activated on the three pages I listed above, so the issue is limited to those pages. It looks the way I want it to look everywhere else. I tried adjusting the code in style.css, but the issue continued even after I cleared my cache.

On a related note, what do you think about whole-site SSL? I've considered it because I know there is a minor SEO benefit to it and, hey, I'll take a minor SEO benefit. 😉 Does it hurt me from a SEO standpoint if external links to our site redirect to the https pages?

[seoskyrocket]

As for the Pingdom issue regarding "minimize request size," I think I'll take you up on the celebration part. 😉

[seoskyrocket]

Actually, I just switched to whole-site SSL and it solved the CSS problem. I've gone through all of my pages to check and I only found a few that show a yellow padlock. I'm looking into those now. Is there anything else I need to beware of now that I've switched over the entire site to SSL? Thanks, again, Dave.

[David Chu]

Ah yes, that's why I saw HTTP elsewhere. 🙂 Doing whole site SSL is probably ultimately a decent idea, but not an enormous big deal right now. I've begun doing research and testing in that area. The most critical thing would be to do it for is for sensitive page info, just as you're doing.

I get a nice green lock on those pages in Chrome. Firefox whines slightly if you read fine print. IE seems quiet about it.

Re: whole-site SSL, you won't get dinged much by Google for being non-secure for quite some time, they're just giving a very early warning.

That bit of CSS looks like it's coming from a familiar plugin. Because it's in the form of a query rather than simply a file, the security police may not like that. If you ditch that and then stick the CSS in style.css instead, I think the problem will go away. If not, then hands-on analysis might be needed. HTTPS, though important, can be a pain. 🙂

D

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[David Chu]

By gosh, you did it! Well, looks like you're all set.

I'd say just do some reading on the topic here and there if you'd like - I'm not a security geek per se. 🙂 Here's an example.

Talk sometime soon,
Best, D

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[seoskyrocket]

As always, thank you, sir!

[David Chu]

😉 Good seeing you! Ciao!

---

Dave Chu · Custom WordPress Developer – likes collaborating with Designers

[seoskyrocket]

Good seeing you, too. Adios, amigo!

[Author]

Posts