Follows-up I32357244c013a2370f14f.
I don't know how or why, but this late way of registering magic
words from within an extension setup function is sometimes
causing people's install to fatally crash on:
> Exception from line 318 of mw/includes/MagicWord.php:
> Error: invalid magic word 'categorytree'
Just move it out of there into a plain and simple registration.
The parser function itself is still registered conditionally.
Change-Id: I07df5de5f39ce0ad029ef0152d126e620308ba25
A performance issue was fixed in the shim(s) generated by
generateJsonI18n.php, so it needed to be updated.
Change-Id: I59e79348275562b5ea0383dea7a7b9923ddccbec
Previously, $wgOut was used when $wgCategoryTreeForceHeaders was set and
a hook was used when it was not.
This change makes sure there is always a hook used with an OutputPage
instance. It fixes bug 57651.
Using $wgOut the rebuildFileCache.php maintenance script would generate
pages without JavaScript and CSS for CategoryTree when
$wgCategoryTreeForceHeaders was set (for example, when the sidebar was
in use).
Other uses of $wgOut in the CategoryTree extension seem to be less of an
issue because when there is a CategoryTree on a page, those pages seem
to be excluded from caching. (But fixing those would be nice
nonetheless: it may prevent other bugs in the future).
Bug: 57651
Change-Id: I0ee66d38755e255c5597db7a237a176039025fae
Extension config based on values of config values isn't going to work
in the global scope. The user won't have set it yet.
Though, is there any reason we don't just loads this always?
Change-Id: I32357244c013a2370f14ff5d36427aa3385be444
Procedure per https://www.mediawiki.org/wiki/Manual:GenerateJsonI18n.php
with shim.
Add a file to .jshintignore to not make Jenkins block on something that's
not related to this patch set.
Change-Id: I9331d328746281a2eb7ec1317d557e8fd7931d74
Load the subtree in the current user interface settings set by the
URL parameters debug, uselang and useskin.
Change-Id: I11c58e62b641c926a9965efb01d776851807e651
Somewhere along the line this extension's JS was refactored,
except for a part which was left as is, and was calling functions
since renamed, and still assuming top loaded...
Just kill $wgCategoryTreeDynamicTag, since it doesn't work, it
hasn't worked for a while, and it looks like a bit of work to
make it work properly. Also change the cache disabling defaults
of this extension to be 6 hours so it doesn't cause explosions.
If someone wants the feature represented by $wgCategoryTreeDynamicTag
they can of course re-introduce it in a subsequent commit. In the
mean time, let's not have broken code.
Bug: 59798
Change-Id: I01e0bd264e2a007cd9de017d10667bb2809d70a9
