Author: swalling
Description:
No worky
Across browsers, UploadWizard just hangs perpetually, on both HTTPS and plain HTTP connections.
Version: 1.22.0
Severity: critical
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=48091
Attached:
Author: swalling
Description:
No worky
Across browsers, UploadWizard just hangs perpetually, on both HTTPS and plain HTTP connections.
Version: 1.22.0
Severity: critical
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=48091
Attached:
[11:33:43.244] TypeError: mw.hook is not a function @ ...
Probably a matter of including the right dependencies in our modules, or maybe we're depending on a version of core not included on Commons right now. Will see what I can do.
iuval.moog wrote:
The same issue seems to prevent most (all?) gadgets on Commons from loading:
https://commons.wikimedia.org/wiki/Commons:Village_pump#Some preference settings are not applied
mw.hook is a mw core module. Confer to https://doc.wikimedia.org/mediawiki-core/master/js/source/mediawiki.html#mw-hook
The debug code has hook included:
http://bits.wikimedia.org/commons.wikimedia.org/load.php?debug=true&lang=en&modules=jquery%2Cmediawiki%2CSpinner|jquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil|mw.MwEmbedSupport&only=scripts&skin=vector&version=20130515T021735Z
But the minified one does not:
http://bits.wikimedia.org/commons.wikimedia.org/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%2CSpinner|jquery.triggerQueueCallback%2CloadingSpinner%2CmwEmbedUtil|mw.MwEmbedSupport&only=scripts&skin=vector&version=20130515T021735Z
Evidence:
http://pastebin.com/yBQNMJ2g line 7114
user: { options: new Map(), tokens: new Map() } }; // MISSING HOOK HERE
}(jQuery));
window.$j = jQuery;
Is there a way to trigger cache invalidation for this particular script so it is regenerated by RL?
(In reply to comment #3)
Actually, I gave you the wrong URI for the minified non-working version. Here is the right one:
note the URI encoded pipe (%7C) between mwEmbedUtil and mw.MwEmbedSupport
It looks like the date is wrong in the "version=20130515T021735Z" term. If the update was tody around 19:00UTC, it should be later.
My main account gets the correct version:
version=20130515T222852Z
(In reply to comment #9)
Thank you.