Discussing SSL and SMF

[nwoGeo]

Use repair_settings.php and change http links to https and click save. I just switched over to ssl and had that problem. That's how I fixed it.

Upload this file to your smf / directory and visit it in your browser. After saving your changes delete it or rename it. I suggest deleting it. repair_settings.php

Also make sure your board url is https://your-site.com and secure cookies are enabled.

[Arantor]

That's funny, I was absolutely categorically assured recently that this shouldn't be a problem (as a prelude to suggesting *this* site go to SSL, and I said this was quite possible... but apparently some browsers don't worry about it)

Which is why I asked for a link to do some investigation...

[Kindred]

it should not be a problem...   so long as *ALL* of the URLs in settings point to the https... (most especially, in this case, the Themes directories settings)

[nwoGeo]

I knew the white screen had something to do with my css file. I couldn't understand why the browser wouldn't load it over ssl. Still don't, It should, right?

[Arantor]

Which is why I asked for a link before you hijacked the topic, to explore and diagnose it.

[nwoGeo]

Which is why I asked for a link before you hijacked the topic, to explore and diagnose it.

LOL too funny.

[Kindred]

it will load just fine over SSL, as long as ALL of the links pointing to it and in it are also https

[Arantor]

Which really sucks on a forum where users can post images that aren't also on SSL

[nwoGeo]

Which really sucks on a forum where users can post images that aren't also on SSL

I thought of that, decided to disable embed images and use attachments instead. Same goes for avatars

[Kindred]

Yes, Arantor... that is true...    the browsers will be choking on errors when imgs call non-ssl addresses

[Arantor]

That's the thing - the guy I was talking to about this demonstrated his site - which is SMF 2.0.6 with full SSL - and a ton of regular HTTP images and browsershots.org demonstrated that the majority of them weren't choking on it.

[Kindred]

hmmm.... odd....

[Arantor]

The point is that browsers are, supposedly, more tolerant of these days. Hence asking for a link to diagnose whether this was a related problem or not before this all got hijacked with a possibly irrelevant solution and a rabbit's nest of discussion as a result.

[Kindred]

true...  therefore Split

[nwoGeo]

I solved the guys problem. There's really nothing to discuss. If you switch to SSL, you have to use repair_settings.php. Bad move splitting it, now this post is irrelevant. Anyone visiting this page from the web, won't make sense of it, but whatever.

[Kindred]

actually, you don't have to use repair_settings.php...   you just have to change the urls to use https...   that can be done in the standard smf admin settings.

[nwoGeo]

actually, you don't have to use repair_settings.php...   you just have to change the urls to use https...   that can be done in the standard smf admin settings.

Please remember that some people actually are starting their first forum. Not to mention, they may not be familiar with all the settings in the SMF admin menu. Not to mention how annoying it is scrolling a theme-less admin menu. all smf internal links have to be switched to https and those options are on different menus. So, the most simplistic way would be to use the repair tool, because once you click save, all is well. From personal experience, you are correct, but in my opinion, it's not advisable.

[Arantor]

Some of us could make the changes without having it be theme less in the first place... From the admin panel. It's about doing it in the right order, or having a more tolerant browser.

[nwoGeo]

"Some of us," I'm guessing those people won't be on here complaining about a theme-less site. This is support right? Not a developers discussion board. Like I said, it's getting more irrelevant and I don't know where this is going. I didn't intend to be the topic starter, it was split after helping somebody.

Now here's the puzzling part for me and I'll leave this at that.

The guy will come back, see a request for a link, may or may not provide the link, then what?

A) Told to use "a more tolerant browser." Then step by step instruct on how to find and change the required links in the admin panel.

or

B) Use repair tool and be done with it.

or

C) link him to this topic.

[Arantor]

There *are* other reasons that things fail, you know. It doesn't just have to be because of the SSL change. I like to be sure about what the problem is before suggesting things.

But it's mostly irrelevant, it just seems easier if I don't bother doing support in future, which would be a shame but it seems easier than dealing with people.