Aside from the fact that some people just generally don't like it, Miraheze is at the point where Special:CentralAuth is taking a considerably long time to load due to the number of attached accounts. For some users, even if they haven't edited that wiki.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 15 2024
Jan 19 2024
Oct 25 2023
Can confirm the above also happens using 8.1, when also using the same extension.
Jul 21 2023
Looks like shutting down the server and booting it back up again fixed the issue. But yes, it probably is the issue above, taavi.
Jun 20 2023
In T339880#8947712, @Reedy wrote:It's helpful if you post the actual error.
To debug this, I've composer depends php | grep 8.1 and it yields, phpspec/prophecy v1.17.0 requires php (^7.2 || 8.0.* || 8.1.* || 8.2.*), which seems to be the package causing the issue—I think. I can't figure out how to remove this and require a version of this dependency that works with 7.4.
^7.2 would include 7.4, upto anything less than 8.0. So I imagine that what you actually thing is the error, probably isn't the error.
See https://getcomposer.org/doc/articles/versions.md#caret-version-range-
Is composer actually running on PHP 7.4?
And do you actually need phpspec/prophecy? It's a dev dependancy...
Jun 19 2023
Jun 9 2023
In T338559#8918955, @Tgr wrote:Can you verify that your vendor/leage/oauth2-server directory has some files? Does vendor/league/oauth2-server/src/Exception/OAuthServerException.php exist? What's the version of the library you are using (you can check in composer.lock)?
In T338559#8917725, @Tgr wrote:In the first approximation, this sounds like a bug in the REST API error logging code. A HTTP 500 should always be logged.
Jun 8 2023
May 31 2023
In T337886#8893551, @gerritbot wrote:Change 925006 had a related patch set uploaded (by Umherirrender; author: Umherirrender):
[mediawiki/extensions/CentralAuth@master] Fix hook runner for CentralAuthSilentLoginRedirect
Feb 10 2023
Is there any update on when this is going to be fixed? Not having this documentation severly hinders extension development for those not familiar with OOUI and the documentation on mw.org isn't really exhaustive.
Feb 2 2023
Swinging back around to this; I brought it up on the mailing list but didn't recieve any feedback.
Jan 9 2023
@Aklapper Thanks, I've "brought it up" on the mailing list.
Jan 3 2023
In T318196#8458150, @Aklapper wrote:@OriginalAuthority: Could you please answer the last comment? Thanks in advance!
Dec 23 2022
In T325830#8488479, @ashley wrote:You should be able to find the git hashes for things downloaded using git on Special:Version, and of course you can always run git log in the appropriate directory to see that (and a lot of other info).
Dec 22 2022
Interestingly, I just downloaded that version of the extension that you linked above and I get the same error.
Dec 17 2022
In T325443#8476067, @Legoktm wrote:Do you have $wgAllowSiteCSSOnRestrictedPages enabled? That allows Common.css to get through safemode.
In T325443#8475892, @Umherirrender wrote:In T325443#8475879, @OriginalAuthority wrote:In T325443#8475862, @Umherirrender wrote:Docs says:
- safemode: Only register modules that have ORIGIN_CORE as their origin. This disables ORIGIN_USER modules and mw.loader.store. (T185303, T145498) See also: OutputPage::disallowUserJs()It does not disable all JS and CSS, it disables all user provided JS and CSS (for example scripts from user pages 'User:<User>/common.js', but also from mediawiki namespace like 'MediaWiki:Common.js' or Gadgets)
Scripts provide by mediawiki itself are still working.It doesn't work, though, from what you're saying, Common.css should also not be loaded, correct? If correct, then my original comment is correct because Common.css is still loaded.
Yes, it includes Common.css.
Works for me with the current master and the latest REL1_39 from gitSteps to reproduce:
- Login as interface admin
- Go to MediaWiki:Common.css and include the content: #firstHeading { background-color: orange; }
- Go to Main Page and the heading should be orange
- Load the Main Page with safemode=1 and the heading is no longer orange
In T325443#8475862, @Umherirrender wrote:Docs says:
- safemode: Only register modules that have ORIGIN_CORE as their origin. This disables ORIGIN_USER modules and mw.loader.store. (T185303, T145498) See also: OutputPage::disallowUserJs()It does not disable all JS and CSS, it disables all user provided JS and CSS (for example scripts from user pages 'User:<User>/common.js', but also from mediawiki namespace like 'MediaWiki:Common.js' or Gadgets)
Scripts provide by mediawiki itself are still working.
Dec 1 2022
Ah, perfect! I figured as much. Looks like I had some errors with Resources.php, all fixed now. Thank you!
Nov 7 2022
Sep 20 2022
Sep 8 2022
I don't see why all of the icons are different sizes? And why is there such a big gap between the alerts and notices icon?