On Wed, Mar 11, 2015 at 7:28 PM, Jason Ji <jason.y.ji(a)gmail.com> wrote:
So it's strange, about ten or fifteen minutes
after I posted that, the
error went away while I was fiddling with something or other. One of those
really strange (and terrible) magically disappearing bugs... so the
following is no longer urgent, but more for my own edification.
Ah, caching issues! If I recall correctly, debug=true bypasses some
internal ResourceLoader caching. debug=false tries to check file mtimes and
such to avoid serving stale caches, but sometimes it gets confused.
For my own local development, I sometimes use a shell script that clears
memcached and redis and runs the clearMessageBlobs.php script from the
WikimediaMaintenance extension. You probably wouldn't want to do all that
on a production server, though.
You're right that I never load mediawiki.api.
(However, I'm still not
loading it and the problem has resolved itself.) But why would I need to
load mediawiki.api, and not other mediawiki JS modules? I've been able to
getting tokens, or mw.config to get various $wg variables).
Some stuff is loaded by default, but I don't think mediawiki.api is part of
that. For something as commonly used as mediawiki.api, though, you might be
getting lucky in that something else on the page might be loading it for
Brad Jorsch (Anomie)