| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
Bug: T122754
Depends-On: I8b46e5232b9a40390143d04577c9356fb03cf23e
Depends-On: Idcad2af992e46a1fb67ac66ca3fcbe9d6fa681a1
Change-Id: I3f125ff432d45f0fdb36076183e01954bc3f84e9
|
|
|
|
|
|
|
| |
Not used anymore anywhere, and deprecated since 1.20.
Bug: T122754
Change-Id: Idbfa8cedd89b1527a4eca254326e20d050175041
|
|
|
|
|
|
|
| |
Swap to 3.6.5 or later based on WMF usage
Bug: T123436
Change-Id: Ie17783ed3985eb05d78759f9469b1a6a198ef26e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bot passwords are something like OAuth-lite, or Google's application
passwords: the bot can use API action=login to log in with the special
username and password, and will then be allowed to use the API with a
restricted set of rights.
This is intended to provide an easy migration path for legacy bots and
for bots on wikis without OAuth, since AuthManager is going to greatly
complicate non-interactive authentication. If OAuth is available, an
owner-only consumer would be a better choice.
Bug: T121113
Change-Id: Iaa4015e00edbfbfaedcc8b2d27a2d3fd25009159
Depends-On: I7e15331efb162275c4116bcae61f19d6b884cbe3
|
|
|
|
|
|
|
| |
This also adds code to User to allow SessionProviders to apply the grant
restrictions without needing to hook UserGetRights.
Change-Id: Ida2b686157aab7c8240d6a7a5a5046374ef86d52
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SessionManager is a general-purpose session management framework, rather
than the cookie-based sessions that PHP wants to provide us.
While fallback is provided for using $_SESSION and other PHP session
management functions, they should be avoided in favor of using
SessionManager directly.
For proof-of-concept extensions, see OAuth change Ib40b221 and
CentralAuth change I27ccabdb.
Bug: T111296
Change-Id: Ic1ffea74f3ccc8f93c8a23b795ecab6f06abca72
|
|
|
|
| |
Change-Id: I38c7d710f489c54592876e7dbc16bf2871e77930
|
|
|
|
|
| |
Bug: T11501
Change-Id: I092d247e72f73c3317a8e6321fd28f8455e598b7
|
|
|
|
| |
Change-Id: Idf0cef999d798c935596e2a784b7d78a8e39f1cb
|
|
|
|
| |
Change-Id: I0ce18bce2d9b5787221e2dabff143de9792abb3a
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: T49162
Change-Id: I57c8887c00cb3b73367e6733af1bf93dbab0c639
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With the great help of:
@reedy <reedy@wikimedia.org>
@MtDu <justin.d128@gmail.com>
@Unicornisaurous <crazy4sb@gmail.com>
@Victorbarbu <victorbarbu08@gmail.com>
and anyone I forgot (sorry), we did our best to find and replace any usage
of the remaining extensions, that use these functions (as you can follow in
the linked task).
Now, finally, these functions were removed from MediaWiki :)
Bug: T70750
Change-Id: Ie9e3d247bf6ab1234ff4f11383d5a4fdf7563397
|
| |
| |
| |
| |
| |
| | |
Maxlag param for wfWaitForSlaves has been deprecated.
Change-Id: I61c09266848e248a28510e267e73ff7177d51bc0
|
| |
| |
| |
| |
| | |
Bug: T122754
Change-Id: Ibb895855aa1bf6b9cbbaf68643362ea485e0427c
|
| |
| |
| |
| |
| | |
Bug: T122754
Change-Id: Ie28dda59cdc450644f7330135b4d43e036d07bf1
|
| |
| |
| |
| |
| | |
Bug: T70750
Change-Id: Ie8ac70454778b1af7f9dc7026e6dd9749c2abae0
|
| |
| |
| |
| |
| |
| |
| | |
Deprecated since 1.22 and not used in any extension
hosted in Wikimedia git (and afaik elsewhere).
Change-Id: I0974ba80b7ab21b056d7f16e936b5c564b562e6d
|
| |
| |
| |
| |
| | |
Bug: T70750
Change-Id: I295b451ecbf765d4c10d90a8373a96b88b8f4115
|
| |
| |
| |
| | |
Change-Id: Id0fe255fd65403d02498f5a98292c560d39dd95a
|
| |
| |
| |
| | |
Change-Id: I22b8445db8f52ffd6bc4a91d3441be9e5197a8a5
|
| |
| |
| |
| |
| |
| | |
No usages anymore in any code hosted on wikimedia git.
Change-Id: I16d1afad211f00b9138219bcf62e5903513169be
|
| |
| |
| |
| | |
Change-Id: Iae5614a82681317afd1b96bc9ab1709fa3588539
|
| |
| |
| |
| | |
Change-Id: Ib8ab894e01b5125207a6f1ac7377c8287b0a8fce
|
| |
| |
| |
| | |
Change-Id: Ibce32556b8213a36876dcb4c6f385afa6e6875aa
|
| |
| |
| |
| | |
Change-Id: If5bdf84b94fec928387ee12492fbec1f511ca059
|
| |
| |
| |
| |
| |
| |
| |
| | |
All callers use method_exists() to call it
Then include ancient jquery themselves...
Change-Id: I7e270abc7b052156ed1e1793269595a647797526
|
| |
| |
| |
| | |
Change-Id: I7602ab7609b13b807e67296c8ce0a1d184c88521
|
| |
| |
| |
| | |
Change-Id: Ie25b69e14155869ff0374a49f1ec3806f026da9d
|
| |
| |
| |
| | |
Change-Id: I9ff1d601cf5fc3402f22bdaf829ae2e287652d31
|
| |
| |
| |
| |
| | |
Bug: T70750
Change-Id: I8c641f5698da2b1ad18d3285b5705d3fe9a3e655
|
| |
| |
| |
| | |
Change-Id: I5c17a57042025b2f72083a97034a5a2dd6c8cfb5
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use the Maintenance class's new $orderedOptions and support for
passing options multiple times. This allows for option "chaining".
The BackupDumper and TextPassDumper class now extend Maintenance, but
should continue to function as before. The public function processArgs()
has been removed and replaced by processOptions(), which takes no
parameters. It is unlikely that users of these classes were calling
processArgs.
Inheritors of these classes that overrode processOption() will now need to
override processOptions() and use Maintenance::getOption() and friends.
The maintenance/backupTextPass.inc file has been deleted. Users should
include maintenance/dumpTextPass.php instead.
Bug: T122587
Change-Id: I2473ee119c185d1b2b00ac4b1e70ee8a6cafe4a3
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code handling this option, added in r14151 / 64cbfd80b576, used to call
dl() to allow use of the utfnormal library's custom PHP extension even if
it is not enabled in php.ini. That part was removed in 1.22 (d0c8ba037cf6).
And as pointed out by Ariel Glenn[1], the utfnormal library later dropped
support for that PHP extension in 6c61fd7c7843 (in favor of intl, which had
already been supported since 1.17 (r69626 / f08147c313f5)), so there is now
no reason whatsoever to check for utf8_normalize(). The option will now be
treated like any other unrecognized option and will be silently ignored.
[1]: https://phabricator.wikimedia.org/T94277#1680209
Change-Id: I467bf609fda6e923fd2d654400d8e1b6c3714d96
|
|
|
|
|
|
|
| |
Deprecated since 1.25
Moved some other API related removal notices
Change-Id: Ibbff6092a10df33f1641f18946765d0032199308
|
|
|
|
|
|
| |
Deprecated since 1.24
Change-Id: Id3357ccd8b5eb3f5e2fe1c63fc7b72ae38d6ac1a
|
|
|
|
|
|
|
| |
All deprecated since 1.24.
Change-Id: I8cf91a12d564dc6b2c48ead5f3f382bebb0217bc
Depends-On: Id788b8f1dbf5b4b7079d361eb1357b3ae942d89d
|
|
|
|
| |
Change-Id: I734e9637317c0737e96e963bafb10ef966d6d172
|
|
|
|
|
|
| |
All usages in extensions are removed
Change-Id: Ie03c384730f59a67a969aed0a866e2bf71247e87
|
|
|
|
| |
Change-Id: Iaa1be8b3f5191edd45e3b0fb7ef1d96951848f7b
|
|
|
|
|
|
|
|
|
| |
It's been a while since clients could reliably construct the cookie
values from these parameters, and it's only going to get worse. So let's
just kill them; the first step is to mark them as deprecated.
Bug: T121527
Change-Id: I6a1a0c7e253e4c651bc0149e956f8767ee6e8b80
|
|
|
|
|
|
|
|
|
|
|
| |
* Skin::getNamespaceNotice: I7567582924757b97b94f757170bc67b18e4ca089
* wfIsConfiguredProxy: I3c1e1d00b93320cde9b39c183174e7a495f03854
* wfDebugTimer: I7b6516f82344f98aaec04bc3af3c208b63169a77
* wfIsTrustedProxy: I86439a772e036dcd5ebdd8b16010c7bacfd9463b
* wfGetIP: I3b8f4b034e23a56f586993549cc5460b28bf6fa7
* MWHookException: I9cf80f2b701d6db8a6cfe884e4fd15d4e0482dda
Change-Id: Ib5359ee50e42f68e8d1985476c5c2d8146a2d8d5
|
|
|
|
|
|
| |
No longer used as of 5d5b269e0e63641f3.
Change-Id: Ieb8448185cf39aa396e902e025e673f0886ac3c3
|
|
|
|
|
|
| |
No longer used as of Ia9131f570.
Change-Id: If009e2620e59002e127d21b90a96bdd29e5d2a9d
|
|
|
|
|
| |
Bug: T113192
Change-Id: I89deb4f8143c1cc6154cdd05bcee1f49d3e3a75a
|
|
|
|
|
|
|
|
|
|
|
| |
* All updates for an event are atomic for the main DB.
* This follows-up 9e51328790c0a by reverting the auto-commit
behavoir which was a side-effect of that change.
* Added TitleMoveCompleting hook with is a pre-commit version
of the same hook. Various extension could benefit from the
atomicity of running in the main transaction.
Change-Id: Ife5990bbedca1de78bcf83f2d6fdeeae8086ffad
|
|
|
|
|
|
|
| |
Mention that $wgSharedDB, $wgSharedTables, and $wgLocalDatabases must be
set consistently for LocalIdLookup to work with shared user tables.
Change-Id: I92d231b78bf7e4fb05b59d0baf69a65b2f728bf7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All unused:
* $wgProfileCallTree
* $wgProfilePerHost
* $wgUDPProfilerHost
* $wgUDPProfilerPort
* $wgUDPProfilerFormatString
* $wgStatsMethod
* $wgAggregateStatsID
* $wgStatsFormatString
The only one still used was $wgProfilePerHost.
Also move release notes for ade945b97a51 from HISTORY to RELEASE-NOTES (Oops!)
Change-Id: Ia0280d23674ace1ac33aa561b06ee73cab865b29
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a low level catch-all net for huge updates that still slip
through. Features that let users add/remove arbitrarily many rows
to lists of arbitrary size can easily result in high lag due to
strange usage patterns or deliberate attacks.
Also removed duplicate 'autochange-username' JSON key.
Bug: T95501
Change-Id: I58a91ca23cae528ef1954d2d78c8f0a90681983e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Anything that wants to be "central" right now has to depend on
CentralAuth, and then either can't work without CentralAuth or has to
branch all over the place based on whether CentralAuth is present. Most
of the time all it really needs is a mapping from local users to central
user IDs and back or the ability to query whether the local user is
attached on some other wiki, so let's make an interface for that in
core.
See I52aa0460 for an example implementation (CentralAuth), and Ibd192e29
for an example use (OAuth).
Bug: T111302
Change-Id: I49568358ec35fdfd0b9e53e441adabded5c7b80f
|