Thread history

From Talk:Main Page
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
21:58, 3 March 2019 MultiplyByZer0 (talk | contribs) New reply created (Reply to is wiki css broken?)
21:57, 3 March 2019 Enamel 32 (talk | contribs) New reply created (Reply to is wiki css broken?)
15:35, 3 March 2019 Skilgannon (talk | contribs) New reply created (Reply to is wiki css broken?)
07:15, 3 March 2019 Xor (talk | contribs) New reply created (Reply to is wiki css broken?)
07:15, 3 March 2019 MultiplyByZer0 (talk | contribs) Comment text edited  
07:01, 3 March 2019 MultiplyByZer0 (talk | contribs) Comment text edited  
06:55, 3 March 2019 MultiplyByZer0 (talk | contribs) New reply created (Reply to is wiki css broken?)
02:41, 3 March 2019 Xor (talk | contribs) New reply created (Reply to is wiki css broken?)
19:07, 2 March 2019 MultiplyByZer0 (talk | contribs) New reply created (Reply to is wiki css broken?)
18:13, 2 March 2019 Beaming (talk | contribs) New thread created  

is wiki css broken?

When I look at discussion threads, I do not see anymore separate post highlighting? The whole discussion with action links now looks like one a single continuous stream.

Does anyone else experience it?

Beaming (talk)18:13, 2 March 2019

I experienced the same bug two weeks ago. But it seems fixed for me now, even though I didn't do anything.

Perhaps it's an intermittent issue?

MultiplyByZer0 (talk)19:07, 2 March 2019
 

The issue seems to be with the js resources which fails to load

Xor (talk)02:41, 3 March 2019

I have a theory about the root cause of the problem, but I need more data to confirm.

Can someone experiencing this issue please open the browser console (F12 -> Console tab), and post the contents of it? Also, which browser are you using?

If I my idea is right, you should see Uncaught ReferenceError: jQuery is not defined.

MultiplyByZer0 (talk)06:55, 3 March 2019

Same here. That's why I suspect the cause is js resources. However this issue seems to happen some time, and disappear some time. Maybe browser caches that once it successfully loads.

Xor (talk)07:15, 3 March 2019
 

I see something else in Firefox:

SyntaxError: illegal character load.php:1:190

When I go to

view-source:http://robowiki.net/w/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=20140108T004349Z

After character 190 it is a bunch of strange characters. I guess something was corrupted on the database?

Skilgannon (talk)15:35, 3 March 2019

Yeah, it looks like jQuery is missing a byte somewhere.

Enamel 32 (talk)21:57, 3 March 2019
 

It seems there are two separate problems then.

Everyone who sees Uncaught SyntaxError: Invalid or unexpected token is:

  • Using Monobook (the default skin), either by choice or by not being logged in.
  • Experiencing this problem continuously.
  • The root cause is that this script, which should contain jQuery and MediaWiki frontend code, has parts of it overwritten with 155648 0x00 bytes.
  • Because that script does not parse, the loading process is broken.
  • This probably requires a server-side fix.
  • People seeing this: Skilgannon

Meanwhile, everyone who sees Uncaught ReferenceError: jQuery is not defined is:

  • Using the Vector skin.
  • Using Chrome.
  • Experiencing this problem intermittently.
  • For the Vector skin, this script, which contains jQuery and MediaWiki frontend code, it perfectly fine.
  • However, that script is loaded by this script through document.write() of a <script> tag.
  • Chrome is known to block the use of document.write() to load scripts on slow Internet connections.
  • Thus, since the script that contains and exposes jQuery is not loaded, other code that depends on it errors with Uncaught ReferenceError: jQuery is not defined.
  • Possible fix: Go to chrome://flags, set "Block scripts loaded via document.write" to "Disabled", and restart your browser.
  • People experiencing this: Xor and past me
MultiplyByZer0 (talk)21:58, 3 March 2019