User talk:ZooWiki

Missing extension

Hi Admin! In the course of remediating some of the issues with {{Infobox medical condition (new)}} I ran into an issue that can only be solved by the installation of a pretty common extension for MediaWiki instances. My suspicion is that it would come in handy fairly often going forward as we continue to de-Wikipedia-ify this place. Where do you stand on the possibility of tackling this? Would the offer of doing the work myself impact your stance at all?

Anyhow, I'm really enjoying my time here so far; thank you kindly for welcoming my involvement! — SockyPaws (talk) 03:22, 27 September 2024 (UTC)

*grins sheepishly* …and could we make it a double order, while we're at it? Extension:JsonConfig is needed by Module:TNT, which is needed by Template:Columns-start and the rest of the Columns template family. 😇 — SockyPaws (talk) 21:25, 29 September 2024 (UTC)

Hiya!

Sorry for the delay. Those can be a good idea. I'm open to some new changes. Getting some dependencies it says it should need and I'll get those plugs installed. On your first message, that explains why certain info boxes were not working the way I was expecting.

Humbled by your trust—thank you.

I just saw my new user rights group memberships and naturally wanted to thank you for the show of confidence. If you have any goals you're especially intent on realizing for this place, please do share them with me if you'd like and I'll do my best to pitch in however I can. 😊 — SockyPaws (talk) 06:27, 26 August 2025 (UTC)

Bloody-stinking-Lua…

The Lua interpreter seems hosed on pages with a lot of templates or citations (see Human sexuality as one potential reproducer), and I believe it has to do with $wgScribuntoEngineConf['luastandalone']['cpuLimit'] in LocalSettings.php being set too low or not being set at all; that key controls the CPU time limit per caching run and accepts whole integer values representing seconds. At least fussing with that value was what ended up fixing this exact error message when it happened over at Kodi Wiki many many moons ago. If it does happen to be unset, I'd probably try putting it in the vicinity of 20–30 and then finesse it from there (I just remember at the time the fallback value I found in the Mediawiki code that's used when it's unset was laughably conservative, like 9 or thereabouts, but don't quote me on that…it was eons ago). If that's not it, then perhaps $wgScribuntoEngineConf['luastandalone']['memoryLimit']? Also, don't forget $wgScribuntoEngineConf['luastandalone']['errorFile'] = '/writable/path/to/file'; can always be put in there, at least while you're tinkering, to introspect what exactly is stalling. (My money's on the DPL3 extension, but that's more out of the long history of bad blood between me and that particular extension than any real insight into the situation, knowing nothing about the current config. 🤬)

And if you do, in fact, find yourself with that file open in a text editor in the course of squashing this bug, could I impose on you to also toss these two definitions in there while you're at it?

$wgAllowUserCss = true;
$wgAllowUserJs = true;

If you hadn't guessed already, I code monkey to keep the lights on over here and I'm desperate for some dark mode on this site to spare my poor battle-weary eyes. It'd just be for me, not site-wide. I've already got things set on my end at User:SockyPaws/common.css and User:SockyPaws/common.js, if you want to take a look, but they're not sourced unless those two keys have truthy values.

Alright, time for me to go hit the sack. I hope all is splendid with you, as always. Wishing you the merriest and zooiest of holidays!

P.S. The search box stopped displaying matching page names while I'm typing in it a little while back. Any idea why?— SockyPaws (talk) 12:52, 25 December 2025 (UTC)