What happened to your web guys?
The glorious mwomercs.com site looks like this since the server migration, which is a rather long time for such a big game.
I have reported this to Mister Niko Snow himself, but it seems like there is no fix.
Pro tip for the annoyed forum user:
Changing the protocol from http to https manually fixes the issue for the current side.
I hope this gets fixed soon so I can buy the fancy new clan mechs
1
8 replies to this topic
#1
Posted 17 September 2014 - 03:09 PM
#2
Posted 17 September 2014 - 10:59 PM
I've been having similar problems (Windows 7, Chrome). Curiously, my mobile (also running Chrome on Android) isn't affected, just any PC I use.
#3
Posted 17 September 2014 - 11:50 PM
Yeah, I can confirm that. And it's broken on iPad, too.
#4
Posted 18 September 2014 - 04:49 AM
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:
...which, when opened separately, has useful text.
On the other hand, this forum page contains this slightly different line:
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!
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!
#5
Posted 19 September 2014 - 03:28 AM
Just to update, //static.mwomercs.com/css/mwo.2.css is no longer a blank document (for me at least), and my web page looks fine again.
Edit: Aaaaand it's gone again. Not sure what the change was.
Edit: Aaaaand it's gone again. Not sure what the change was.
Edited by Sparks Murphey, 19 September 2014 - 04:19 AM.
#6
Posted 20 September 2014 - 03:28 PM
Atm it works well for me but i have no clue if it stays that way...
#7
Posted 20 September 2014 - 05:43 PM
This is happening to me too - the workaround is to add https:// to the beginning of any url on the site but you have to do that each page load :/ I'm on firefox/Win7 64
#8
Posted 20 September 2014 - 07:08 PM
Muffinator, on 20 September 2014 - 05:43 PM, said:
This is happening to me too - the workaround is to add https:// to the beginning of any url on the site but you have to do that each page load :/ I'm on firefox/Win7 64
Yeah, that workaround forcibly inserts https:// into all the URLs referenced on the page, thus fixing the CSS pointer.
#9
Posted 21 September 2014 - 06:11 AM
Bump because bug still occuring
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users