@brion There's a possibility it's actually an api.php issue -- is that something you're more familiar with? I'm doing a debug-trace-log to figure out what's going on, and... the trace suddenly stops when it tries to get a new ApiMain... mysteeeerious [waggles fingers]. 🎩
@woozle hmm, could be a thing where somethign changed internally to ApiMain and had to be updated in MediaViewer -- are the versions in sync? (We're really bad about keeping old compatible versions synced, so latest is greatest.)
Feel free to drop error details by dm etc, I'll see if I can divine any details.
@brion Looks like this one was my bad -- trying to print_r() the value of $processor was eating up all the RAMs.
...and now the log files aren't being generated at all; obviously I've mucked something up somewhere...
Well, now (after getting the logging working properly) it seems everything is going hunky-dory in api.php, and I'm back to having no idea what the problem is.
Where would I check to be sure I've got the same versions? The MW I'm running was downloaded from the usual download packager...
(MW v1.36.1, but the MultimediaViewer extension just shows "--" in the version column, so...)
Okay, latest fun discovery: if I make the site public (temporarily), then load the page in a private window, everything works. If I shift-reload it when logged in (even with the site public), however, it still doesn't work.
Gotta go afk for a bit, but.... arrrgh.
@woozle well I'd check that they were checked out from source control on the same branch on the same day. No idea if MediaViewer of any version will reliably work except on trunk or not.
@woozle reload vs shift-reload sounds like a resourceloader problem — either a bad entry is cached (might be fixed when you get back) or it’s a differential error (might be traceable at least!). ahhhh computers they’re so fun ;)
@brion I wasn't distinguishing between reload methods; I tried to do shift-reload whenever it mattered... but I may not have been 100% consistent.
The main distinction was:
wiki public, anon user: WORKS
wiki public, logged in: NO GO
...and of course it's not working for either of those with the wiki private, but I can't test it for anon user because anon user can't see anything at all.
Hmm, I suppose I could try whitelisting that page... not sure what that would tell me, but at this point I'm grasping at straws.
@woozle :( hmm, anything visible in the api requests & responses in network panel in dev tools?
@brion I need a quantum computer (and brain) so I can try All Of The Things at once...
No-go with the whitelist. Now testing current official 1.36 release of MMV. Then will see if I can figure out what's going on network-wise (good idea, that).
@brion There are some 304 codes, but I can't see that they're actually causing a problem. That said, I don't feel adequately educated on how to use that tool.
Newly-discovered weirdness, with the requisite pages whitelisted:
logged in: NO GO
logged out: NO GO
private window: works o.0
I've tried clearing cookies and stuff, but still it can somehow tell the difference between a browser that has been logged in and one that has never been logged in.
I should check under the couch for my mind; I've obviously lost it...
I should try with a fresh browser: check it anonymously, then log in and check it, then log out and check it again.
Giving up for now; I really just can't justify the time to look into this any further when I've got at least five other project-wolves at the door howling for attention.
(They've been waiting a long time now. They're hungry.)
It almost seems to be random: I went into a completely different browser, and now it won't work at all, under any circumstances as far as I can see.
It seems likely there's some confounding factor (a cache somewhere?) that is preventing me from reliably seeing the effects of changes that I make.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!