aboutsummaryrefslogtreecommitdiffstats
path: root/includes/config-vars.php
Commit message (Collapse)AuthorAgeFilesLines
* Add UserGroupManager::getUserPrivilegedGroups()Gergő Tisza2023-09-041-0/+6
| | | | | | | | | | This moves the core part of wfGetPrivilegedGroups() out of Wikimedia config and makes it possible to move functionality built on it into core. Bug: T208477 Change-Id: I6536ef2909caeed047447e8b6a25831d6f00d827 (cherry picked from commit 7a21b9a03271d5857f2f059adcaf2b9df4a8355c)
* rdbms: Remove deprecation mark for $wgSharedDBTimo Tijhof2023-01-121-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | This was marked as deprecated to indicate that it shouldn't be used to share arbitrary database tables between wikis. However, this has never been officially supported and so doesn't actually warrant deprecation. The only use case for $wgSharedDB that MediaWiki supports (and even encourages in documentation) is for global accounts shared between wikis. Recently, update.php started to block upgrades when a deprecated setting is used, which has brought this otherwise-innocent deprecation comment to light. Remove it as such since the feature for which it exists isn't deprecated, and we don't have any other (supported and documented) ways of sharing accounts between wikis. In the future, we might rename this and turn it into a boolean so that it is easier to understand and maintain, but that's for another day. Bug: T308536 Change-Id: I1598630f2ab2c9bd443a5f3e6fc0997ceb52c5b2
* ResourceLoader: Remove $wgIncludeLegacyJavaScript and simplify codeTimo Tijhof2022-09-141-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the deprecation of wikibits.js originally started, it contained a ton of things [1] such as: * user-agent utils, `clientPC` and `is_gecko`. * addOnloadHook. * importScript. * appendCSS. * stylepath and other config vars. * tooltip, e.g. updateTooltipAccessKeys. * portlet, addPortletLink. * tablesorter, e.g. ts_makeSortable, ts_getInnerText * searchsuggest. * notify utils, e.g. jsMsg. * spinner utils, e.g. injectSpinner. * event utils, e.g. hookEvent. * siblings scripts included: mwsuggest, sajax. Except for two (addOnloadHook, and importScript), these have all found new homes and been succesfully migrated and replaced over the years with other platform APIs. The $wgIncludeLegacyJavaScript variable hasn't been needed for a while as what it gated no longer exits. Remove it and fold the two remaining functions into mediawiki.base as defacto stable APIs. * addOnloadHook: Not worth breaking imho. I've shortened the implementation which saves a few bytes in WMF prod, and adds a few bytes for CI/third-party where it was previously absent for new wikis (thus reducing portability). * importScript: Never deprecated in the first place as there is no mw.loader equivalent to this. In order to achieve optimal cache performance, and benefit from automatic purging after edits, one must craft a very specificly encoded and ordered canonical action=raw URL. This is not something end-users need to know about, and is what imporScript exists for to abstract. Plus, it ensures de-duplication. One day something like Gadgets 3.0 (T36958) might take off, but for many years to come, importScript remains the best and only supported and usable means within the platform to share and load user scripts. Tested with: `curl 'http://localhost:8080/w/load.php?modules=mediawiki.String%2Cbase%2Cuser%2Cutil&skin=vector' | gzip -9 | wc -c`. Before: 9.53KB After: 9.45KB [1] https://gerrit.wikimedia.org/g/mediawiki/core/+/1.17.0/skins/common/wikibits.js [2] https://www.mediawiki.org/wiki/ResourceLoader/Migration_guide_(users) Change-Id: I10f17f68fea862d510d188b927f4a7b38be0e4a4 (cherry picked from commit 0ff333e2ffe4e51eba31f86877af1a67d726e320)
* Support CDN query parameter re-orderingOri Livneh2022-08-091-0/+6
| | | | | | | | | | | | | | MediaWiki sets a large 'Cache-Control: s-maxage=' directive on page views only if the request URL matches one of the normal CDN URL forms. When MediaWiki is behind a CDN that re-orders query parameters on request URLs, we want the CDN URL matching logic to be insensitive to the order of query parameters. This change introduces a 'CdnMatchParameterOrder' configuration option that can be used to control this behavior. It defaults to 'true', which preserves the existing behavior (order-dependent matching). Bug: T138093 Change-Id: I3c52ca47e095ba32511892853dac6c87a1cc2321
* Skin: Remove schema leftover for removed $wgFooterLinkCacheExpiryTimo Tijhof2022-08-021-6/+0
| | | | | | | Follows-up 1fa903a2110 (I581c49839ab4). Bug: T313462 Change-Id: Id2c7043fb89d59026dacefbdf1599e6cbf9ef418
* Remove Flash cross-domain policy manglingTim Starling2022-07-221-0/+1
| | | | | | | | | | | | Remove Flash cross-domain policy mangling. Users who are somehow still using Flash as a browser extension will be exposed to CSRF vulnerabilities. Deprecate the config since deprecation has some advantages in the new config system over simple removal. Bug: T279496 Change-Id: I2c0e85a430d7e6aaf8d5decd00cf1dade04cebe1
* Fix type declarations in MainConfigSchemadaniel2022-07-151-4/+0
| | | | | | | | | | | Validating against the live schema on the WMF cluster exposed several issues with the config schema. Mostly settings declared to be lists which are actually associative arrays. This also removes deprecation markers for some settings that are still in active use, just discouraged or unstable. Change-Id: I63e816edd1a561bda6063f8558ccce88c113df3f
* SettingsBuilder: report warningsdaniel2022-07-151-1/+0
| | | | | | | | | | | This adds functionality to SettingsBuilder for collecting warnings to be logged later, when the logging mechanism has been set up. This also adds a validation step to update.php that aborts the update if any warnings have been registered in SettingsBuilder, or the settings fail to validate against the settings schema. Change-Id: I387905289fb93591f79b96bf4c6cb5ec692b2aff
* Introduce new WRStats library for write-read statsTim Starling2022-07-051-0/+6
| | | | | | | | | | A library for storage of counter value time series statistics, based around the observation that memcached getMulti() is apparently fast enough to do this in a simple manner, with incremented values stored in time window buckets. Bug: T310662 Change-Id: I26b1cdba0a06ad16ad8bb71b455e1b6180924d17
* ParsoidOutputStash: make storage backend configurable.daniel2022-06-141-0/+6
| | | | | | | | | | This introduces the ParsoidOutputStash config setting, which defines the storage backend and cache duration. The storage backend name refers to an entry in the ObjectCache setting, and defaults to the main stash. Bug: T267990 Bug: T309016 Change-Id: Ic67dc43ed9843810e4b180127f9a3bb7608f7608
* Merge "ParserCache: always use JSON"jenkins-bot2022-06-071-7/+0
|\
| * ParserCache: always use JSONdaniel2022-06-071-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | When JSON support was introduced into ParserCache in 1.36, it was controlled by a feature flag, $wgParserCacheUseJson. The feature flag was "born deprecated" in 1.36. It can now be removed. This means that ParserCache will always store entries as JSON. Support for reading old non-JSON entries remains intact. This is needed when updating wikis from a version older than 1.36 to the current version. Change-Id: Id04e42bfb458d98414bac50e0d6c505e8878e5c0
* | Settings: Generate schema artefacts using a single maintenance scriptdaniel2022-06-051-1/+1
| | | | | | | | | | | | | | | | | | | | Previously, each of the four derived config schema files had to be regenerated using a separate maintenance script. This change simplifies regeneration by combining all for scripts into a single command that can be used to regenerate all relevant files after changing MainConfigSchema. Change-Id: I7d38d8a4aede60475c4bdd0053d2e10e298b9843
* | Merge "Allow sharding in site_stats update"jenkins-bot2022-05-311-0/+6
|\ \
| * | Allow sharding in site_stats updateAmir Sarabadani2022-05-301-0/+6
| |/ | | | | | | | | | | | | | | This would be useful in cases that lots of edits happen at the same time and this would reduce the time waiting to get the row lock. Bug: T306589 Change-Id: I3b869e3b85dfd66575390ef4247f2f81f19c878e
* | Remove unused config $wgInterwikiPrefixDisplayTypesdiesel kapasule2022-05-311-6/+0
| | | | | | | | | | Bug: T306361 Change-Id: Ic6e43d5bbca873dd27e9e2a1f2bc9d0c9a43dfa4
* | Remove unused configuration global $wgLegacySchemaConversiondiesel kapasule2022-05-301-6/+0
|/ | | | | | | | I removed $wgLegacySchemaConversion from config-vars and HistoryBlobCurStub. Bug: T303684 Change-Id: I7f918ab61ffea377bd827721f9b41ae5d8f82226
* ResourceLoader namespace (attempt 2)Tim Starling2022-05-241-2/+2
| | | | | | | | | | | | | | | | | | Move ResourceLoader classes to their own namespace. Strip the "ResourceLoader" prefix from all except ResourceLoader itself. Move the tests by analogy. I used a namespace alias "RL" in some callers since RL\Module is less ambiguous at the call site than just "Module". I did not address DependencyStore which continues to have a non-standard location and namespace. Revert of a241d83e0a6dabedf. Bug: T308718 Change-Id: Id08a220e1d6085e2b33f3f6c9d0e3935a4204659
* Start clean up of revision_actor_temp tableAmir Sarabadani2022-05-231-6/+0
| | | | | | | It is being dropped in production Bug: T215466 Change-Id: I66b2cb8653252e720c897351065978119f040ba7
* parser: Remove Priority Hints experiment for thumbnailsmainframe982022-05-191-12/+0
| | | | | | | | | Both this feature and the web standard are experimental. The standard was only exposed as a Google Chrome Origin Trial and the standard has evolved in a non-compatible way. Bug: T308707 Change-Id: I987c0fb9e3fbb1a9f727b3f171c747246d8adb77
* parser: Remove Element Timing experiment for thumbnailsmainframe982022-05-181-6/+0
| | | | | | | | This feature was experimental, unsupported and untested. It was disabled by default. Bug: T308621 Change-Id: I9375f35d031f635af0d39ee0bc027ac719899d9d
* Turn DefaultSettings.php into a deprecated stubdaniel2022-05-171-0/+4432
DefaultSettings.php has been replaced by MainConfigSchema. Loading DefaultSettings.php is deprecated. Code that needs to have access to configuration defaults should use the ConfigSchema service object. Bug: T300129 Change-Id: I7b2c0ca95a78990be1cdb9dd9ace92f6dcf1af15
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-24 01:02:27 +0000