What can we do better?

[mayer57619]

So...I have now had the formatting troubles.  It works fine in an incognito window, but in a normal one it seems as though the forum is set to view in the archive or lite mode.  I have not been changing any of the theme settings as of yet so not sure why but I will see what I can find.

[RobinK]

So...I have now had the formatting troubles.  It works fine in an incognito window, but in a normal one it seems as though the forum is set to view in the archive or lite mode.  I have not been changing any of the theme settings as of yet so not sure why but I will see what I can find.

Read what I wrote above. Delete selectively to avoid getting logged out of all sites. For me, 1 hour did the trick.

   

[mayer57619]

RobinK. That is what I did and it works fine. I am trying to figure out why it happens in the first place as it seems widely variable to who and when it occurs.

[GAW9576]

I am using the latest version of Chrome on my hp laptop, and TOST is not formatted, it is wonky and very hard to decipher. This is what I am seeing: https://i.postimg.cc/6phFQY9p/tosthome.jpg

That's what mine looked like too. I guess I'm just used to having to clear everything periodically and logging back in. I've always had one issue or another with ever browser and every computer/cellphone I've had.

[RobinK]

RobinK. That is what I did and it works fine.  I am trying to figure out why it happens in the first place as it seems widely variable to who and when it occurs.

I'd start with the broken SSL setup. If you alter the address from http://www.tost3.com/ to https://www.tost3.com/, the error will reproducibly occur. Any browser that defaults to https:// (someone mentioned the DuckDuckGo browser which, if memory serves, uses https everywhere) will run into trouble. Get rid of the unencrypted connection and you should be good to go. Me, I'll delete some cookies now to get back the CSS files...

[GAW9576]

RobinK. That is what I did and it works fine.  I am trying to figure out why it happens in the first place as it seems widely variable to who and when it occurs.

I'd start with the broken SSL setup. If you alter the address from http://www.tost3.com/ to https://www.tost3.com/, the error will reproducibly occur. Any browser that defaults to https:// (someone mentioned the DuckDuckGo browser which, if memory serves, uses https everywhere) will run into trouble. Get rid of the unencrypted connection and you should be good to go. Me, I'll delete some cookies now to get back the CSS files...

Yep. I had to go and try adding the s after HTTP just to see for myself. It made everything weird again.
Of course I tried logging out and in again and it was still weird so I had to clear everything and log in again now everything is fine. I'm the one on Duck Duck Go. You may have already answered this and I didn't understand but Is there anything I can do to prevent the issue.

[riverrun]

And it's broken again.
Deleting cookies just for tost3.com doesn't help.
HTTPS is the problem. Fix it or remove it.
Then message me. Thanks.

[RobinK]

Could whoever is in charge of the web server try this, please? It's from MyBB Documentation - Setting up HTTPS. And if you open a browser console and analyse the content delivered when you load https://www.tost3.com/, you will see that (at least, I didn't check any further) the CSS is delivered via http instead. This would explain the weird look of the site, because that's what the site looks like without the CSS.

Removing mixed content
Mixed content (insecure content) occurs when the initial page is delivered over HTTPS, but includes content (such as images, videos, etc.) downloaded through insecure HTTP, limiting the security benefits of HTTPS (read more).
Templates and CSS
Some resources, like images, CSS or JavaScript files might be loaded through your MyBB theme’s CSS files (Templates & Style → Themes) and templates (Templates & Style → Templates). Those are usually located in the headerinclude template (Ungrouped Templates). You can also use the Search/Replace utility to find all occurrences of 

Code:

http://

 to replace it with 

Code:

https://

, making sure these resources work correctly under the new address first.

[mayer57619]

Lets try thing set up this way...hopefully I got it straightened out, but only time will tell.  Sorry for the troubles.

[RobinK]

Encryption works now. Thanks, Justin.