27 replies to this topic

[VIPER2207]

Could someone responsible for this (i.e. PGI Staff) please react to this and give a statement? I'm getting a little upset about this...

[Sparks Murphey]

As I posted over here, it seems to be an issue with the css (cascading style sheet, for those not html savvy) pointing to an incorrect location:

Sparks Murphey, on 18 September 2014 - 04:49 AM, said:

I think I've found the cause after a little digging.

My Profile page is fine, but the forums aren't, so I poked around inside the source code for the pages.

The Profile page contains this line:

<link rel="stylesheet" href="https://static.mwomercs.com/css/mwo.2.css" type="text/css" media="screen">

...which, when opened separately, has useful text.

On the other hand, this forum page contains this slightly different line:

<link rel="stylesheet" href="//static.mwomercs.com/css/mwo.2.css" type="text/css" media="screen">

Note the absence of the "https:" at the front of the URL. This points to a blank document for me.

Other URLs starting with "//" and not with "https://", such as "//mwomercs.com/forums/public/js/3rd_party/lightbox.js", work fine.

Hope that's useful to someone!

[Lucius Vaudois]

Lucius Vaudois, on 13 September 2014 - 10:49 AM, said:

Same problem here. I have it on two different PCs, using Firefox.

All systems nominal now.

[Johnny05]

It's still broken for me unless I set the page to HTTPS. If I click a forum topic or next page in a thread it goes back to HTTP and I have the issue again.

[Thexder]

I'm still having this issue but I am wondering if someone else can try this out. I seem to have fixed it slightly while I was mucking around. Once you log in, go to profile, then go to the MWO directory. Seems to fix the problem unless you go to the forum pages.
Really sick of this issue.

[Thexder]

Well it seems that the planets have aligned and all is good when it comes to the MWO website. Thanks for whoever was able to sort out the problem.

[Sparks Murphey]

Same here, everything seems peachy again.

[cleghorn6]

I confirmed in another thread that using a plugin to force https resolves the problem.