Aahan Krish

And did you notice that Mike gave out his email? mike[at]mvied[dot]com
Maybe he’s available for a charge, check it with him.

.me has probably been created for personal websites (I own aahan.me). Anyway, Dealso.me is a domain hack for Dealsome – – like awesome. (Did you know Delicious, a social bookmarking site? it went by del.icio.us for some time, now it’s delicious.com).

Anyway, coming to the point, you are asking me how to fix those? Seriously? I mean, who created that website, not you? If it’s not you, then you should definitely contact that person.

Because it involves editing wordpress files via FTP (if they were added manually into the template) or via WP-ADMIN if they were induced by some options. So, you should figure it out.

If you want I can take a look, but if it involves lot of hours, then probably I can’t help. (give out your email if you want me to take a look.)

Hey, actually dealso.me domain (as in Dealsome!) is available, did you know? Sorry Mike, I am free today, and am messing up with your support.

??

1. In chrome go to https://www.wheedledeals.com and when’s loaded completely, right-click anywhere on the page and select “View page source” or directly Ctrl+U (or cmd+U).

Now that is the real face of your website. I don’t understand why such a small page has that much code. Anyway, now Ctrl+F and that opens a search box at the top-right corner of the browser. Type https:// and use the arrows to find the https:// links in the page. Try to fix them all by editing the wordpress files or the way you added them.

That’s the way to do it.

2. It’s been an year since I started blogging (bit.ly/cCHRgU), and I’ve learnt a lot as to how a blog or website should be kept – – UNOBTRUSIVE at all times.

As for the translation thing, I am sure there are better ways of doing it. Google is your friend.

From the source of your website I see 43 HTTP:// links. Try fixing them, then it should work.

And why are you using Wibiya? From a my personal point-of-view (visitor), I hate such obtrusion in a page. Something popping out or overlaying is not cool my friend. Just what I think, you need not heed to it. ??

@mike and @wheedle: If I am not wrong, Chrome shows a little triangle if the static files from your website are loading via HTTP. If the static files, or whatever are loading via HTTP via someone else’s website (anyone other than yours) it is considered “not secure” and hence the red X mark.

I came to this conclusion from reading the error (screenshot: https://img1.uploadscreenshot.com/images/orig/8/24118261074-orig.jpg)

However this page includes other resources which are not secure. These resources can be viewed by others while in transit….

Oh yes… Mike’s right. Sorry about my wrong suggestion. I quit. ??

@wheedle : Do you use some sort of caching system? Did you try clearing your browser cache? (That’s where Chrome can be tricky sometimes… but I don’t know, if in this case, it can be).

Otherwise, only Mike can you help you.

@wheedle hehe! It’s nothing to worry about actually. It’s just that some of the files are being loaded via HTTP.

Check these options in WordPress HTTPS (SSL) plugin that you are already using and it should be fixed.

1. Internal HTTPS Elements – – should be checked (tick the box)
2. External HTTPS Elements – – should be checked
3. Bypass External Check – – should be UNchecked
4. Disable Automatic HTTPS – – should be UNchecked
5. Force SSL Exclusively – – should be UNchecked as well

Do that will enable HTTPS (SSL) encryption for your entire website, and should remove that crossed HTTPS mark in the browser address bar.

@mike correct me if I am wrong.

Check what Mike suggested first…

And then, it would also be a good try to disable all plugins. If it works as it should, then enable each plugin, one by one, to find out the culprit.

@mike: Right.
@wheedle: You’d better explain what’s actually not working. Did you even read Mike’s reply to your question?

You'll have to be a lot more descriptive than that. What issues are you having?

@wheedle : Bluehost probably resells SSL certs (if I am not wrong). Anyway, it should be okay with that.

Just confirm one thing. Are you using the development version of wordpress HTTPS? (I think I had similar problems with redirection. Developmental version fixes it.)

You can download it here: https://downloads.www.ads-software.com/plugin/wordpress-https.zip

Okay, thanks for your suggestion Mike. I am looking at both Comodo and Godaddy at the moment.

cheers.

Hey Mike, it’s me again.

wheedle is both right and wrong. Here’s what I’ve noticed on all browsers.

(1) If the ssl certificate is issued by a certified CA authority (you know there are many like Comodo, Go Daddy, Verisign, Thwate etc), then WordPress HTTPS plugin successfully redirects according to the settings in the options page. This because the browser doesn’t have any issues with the SSL certificate of the website.

(2) Some people (like me) use a self-signed SSL as we only need SSL to access WP-ADMIN and not for public use. In this case, the browser doesn’t trust our SSL certificate, and the user will have to manually add our certificate to the trusted list maintained by the browser. (easier in firefox, but tougher in Chrome). Only after doing so, does the browser allow redirection from HTTPS to HTTP.

But this fails the purpose of the plugin for us. We do not want the users to see an error message that our website is not safe/trusted (like this – https://bit.ly/ncGsSE – looks awefully frightening for newbies in Chrome, and they’ll probably close the tab in no time) when they visit via HTTPS link, but that is what is happening despite using this plugin.

So, I see only three solutions here:
– plugin should enable server-side redirection. This issue is probably because the plugin uses wordpress redirection.
– or we pay a few hundred bucks a year to get an SSL certificate from a highly qualified CA authority.
– or maybe there’s another way that you might know.

I could be wrong though. But this is how I believe it is.

thanks.

@ipstenu do you know the reason why our posts are being flagged as spam by the system?

@mvied That relieved me. Thanks. Good day.