| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This hooks allows extensions to override the normal model-specific rendering
of page content. A typical use would be to provide syntax highlighting for
pages that contain scripts. In that sense, ContentGetParserOutput is a
generalization of the old ShowRawCssJs hook.
Change-Id: Ibfb2cbefea44eeee9f2a027f47e7721bf177ba0f
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Currently Title permissions hooks get called after
Title::checkQuickPermissions, preventing users from
overriding quick permission checks. Added a hook to
allow this. Needed for bug 45898.
Change-Id: Id672270741282778815b06eff8b234ca4d819744
|
| |
| |
| |
| |
| |
| |
| | |
Some extensions like PageTriage will be able to use this new
parameter to determine whether to show its own curation toolbar.
Change-Id: I07e85aa37edc994c5a2bf9d011976b91ff01ab14
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change is entirely in local scope.
The function is still called getUsableSkins()
so this change won't break anything.
But the variable name and the updated documentation comment
make it clearer what the purpose of this function is,
for anyone reading the code or reading the autogenerated docs.
This change also includes minor changes to documentation
in skin-related files (typos and small edits for clarity).
Change-Id: I4220408f4d3b64cf87be4ad1af4b72d3a4524922
|
|/
|
|
|
|
|
| |
According to online documentation: "This feature was removed completely
in version 1.18.0."
Change-Id: I410dce8b04ff788cd6573b3b11fd56ce41a96395
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Follows-up I1343872de7, Ia533aedf63 and I2df2f80b81.
Also updated usage in text in documentation and the
installer LocalSettingsGenerator.
Most of them were handled by this regex:
- find: (require|include|require_once|include_once)\s*\(\s*(.+?)\s*\)\s*;$
- replace: $1 $2;
Change-Id: I6b38aad9a5149c9c43ce18bd8edbab14b8ce43fa
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This allows extensions to purge derivative resources that need
updating when a wiki page is changed.
Change-Id: Ic28ce7f57f29376b041627288979981fcb218a44
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Follows-up 97caae596d5493 which makes HTML5 the default
and removes support for XHTML 1.0 and HTML < 5.
* <script type>
* <style type>
* <html xmlns>
* Quick-closing slash in non-XML HTML5 documents
Change-Id: I71855fa8d4095a5a448ebdc3dc36506ddab6f70c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Squiz.WhiteSpace.LanguageConstructSpacing:
Language constructs must be followed by a single space;
expected "require_once expression" but found
"require_once(expression)"
It is a keyword (e.g. like `new`, `return` and `print`). As
such the parentheses don't make sense.
Per our code conventions, we use a space after keywords like
these. We appeared to have an unwritten exception for `require`
that doesn't make sense. About 60% of require/include usage
was missing the space and/or had superfluous parentheses.
It is as silly as print("foo") or return("foo"), it works
because keywords have no significance for whitespace between
it and the expression that follows, and since experessions can
be wrapped in parentheses for clarity (e.g. when doing string
concatenation or mathematical operations) the parenthesis
before and after basiclaly just ignored.
Change-Id: I2df2f80b8123714bea7e0771bf94b51ad5bb4b87
|
|
|
|
|
|
|
| |
Reflect the fact that five of the skins were removed. Some rephrasing
as well.
Change-Id: I1acfa872eb4601003762d29443265a49e2100cd6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This hook allows extensions to disable or modify the new messages
alert ('orange bar of doom') while still allowing the user_newtalk
table to be updated.
The wgUserNewMsgRevisionId JS global allows gadgets and extensions
to create their own new message alerts on the client side.
I also threw in a few comment updates for good measure!
See also Echo change I3f35a56b which utilizes this.
Bug: 47962
Change-Id: I2105bdd2bcd5b27f6f36ec8d8fa7fa99d60a2d82
|
|
|
|
|
|
|
|
| |
Adds a consistent method for authentication extensions to block
password changing operations.
Bug: 46590
Change-Id: I3469e90a958c4fb0f24cafd67de5590d3cc2f075
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a new hook called LanguageLinks which is called
whenever a list of language links is returned to the user.
This gives extensions the option to manipulate the links
on the fly.
Note that this change only covers the language links used
in OutputPage and by ApiParse. Adapting ApiQueryLangLinks is
left as a follow-up task.
As explained on bugzilla, this is a precondition to
allowing Wikibase/Wikidata to update languagelinks without
forcing a (redundant) re-parse of the page content.
This change also introduces the notion of link flags that
can be used to associate flags with language links. This
will be integrated with ParserOutput and OutputPage in a
follow-up.
Change-Id: Iaec0faa131413a291fc8f77496e4f371addb3b99
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changed logic in MWTimestamp::getHumanTimestamp so that
all the message and formatting was offloaded into the
Language class, keeping only actual timestamp logic in
the MWTimestamp class.
Also added a hook so extensions can override the
human timestamp format.
Change-Id: Ie667088010e24eb6cb569f9e8e8e2553005223eb
|
|
|
|
|
|
|
| |
This allows extensions to modify the array.
This completes the serie of hooks for similar get methods in ApiBase.
Change-Id: Ib398f5815ab57f25d56356b0997c55a03fd96874
|
|
|
|
|
|
|
|
|
| |
The recipient is the user who's talk page was edited. Extensions may
want to send or not send the notification based on some aspect of the
user, for example a preference.
Bug: 46550
Change-Id: Ifc8fbaf8fdc96f9c18c2a889d2e854e49b3a7010
|
|
|
|
| |
Change-Id: I1a37ffb0e8cde4deac027721b0e463585b58d634
|
|
|
|
|
|
|
| |
This data is very useful with the hook as it holds the
criteria to build the watchlist query.
Change-Id: I688ab0b35b301f180bbfde3ad3043b1ee602de10
|
|
|
|
| |
Change-Id: I348b449043fefba181e28486a07c4aa761bcef24
|
|
|
|
|
|
| |
This will allow us to easily add other RL modules to the page
Change-Id: I2ec00d44e37298ef91ab428759bda037072b0120
|
|
|
|
|
|
| |
These will allow Echo to add a 'thank' link next to the 'undo' links
Change-Id: Ifb93e49b30bb325ecd17ece9f36bcd83c63a2563
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Spotted in ipbreason-dropdown by Shirayuki.
Change-Id: I576ed4bc0abe5ab980aaee3fb9f9e4b43087311f
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use lowerCamelCase.php format for all files (per [[mw:CC#File_naming]]),
and make filenames more specific:
- clear_stats.php -> clearCacheStats.php
- clear_interwiki_cache.php -> clearInterwikiCache.php
- initStats.php -> initSiteStats.php
- proxy_check.php -> proxyCheck.php
- stats.php -> showCacheStats.php
- showStats.php -> showSiteStats.php
Also changed the class names accordingly (per [[mw:CC/PHP#Naming]]),
and make class names more specific:
- clear_stats -> ClearCacheStats
- InitStats -> InitSiteStats
- CacheStats -> ShowCacheStats
- ShowStats -> ShowSiteStats
Updated files that made references to the changed files/classes:
- DefaultSettings.php and SpecialBlockme.php (proxy_check.php -> proxyCheck.php)
- maintenance/showSiteStats.php (initStats.php -> initSiteStats.php)
- maintenance/README and docs/memcached.txt (stats.php -> showCacheStats.php)
- docs/maintenance.txt and docs/memcached.txt (clear_stats.php -> clearCacheStats.php)
Thanks Hashar for the initial help and encouragement :)
Change-Id: I60f76fc971e06e1b710dcda35f9c2d931b93bdd7
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
My first instinct was to derive the hook signature from the implementation and
have a generic 'PageCategoriesUpdated' hook that receives the WikiPage object
and two arrays ($added, $deleted). After some reflection I decided to iterate
through each array and call the hook once per category. I like this way of
doing things because a change in page membership could be thought of from two
directions: it is either the category that is gaining or losing a member, or
the page that is gaining or losing a category.
The category name is sufficient for instantiating a Category object without
additional queries being needed, so my preference was to pass objects rather
than string identifiers.
If implementors of handlers happen to be interested in the set of categories or
pages being updated, it is still the case that they only need to write one
function, and track state using a class property.
Change-Id: Ica4c5fb3acdea6c00678ec0794808fa50a1dd39a
|
|
|
|
| |
Change-Id: I9b294a213a4000f503c0010d88757db6dda927c0
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* PageSet can now be used in any action to process titles/pageids/revids
or any generator, redirects resolution, and converttitle functionality.
* action=purge proper usage of MustBePosted()
* Add supports for all pageset capabilities - generators, redirects, converttitles to
action=purge and action=setnotificationtimestamp
* BREAKING CHANGE: ApiPageSet constructor now has two params instead of three, with only the
first one keeping its meaning. ApiPageSet is now derived from ApiBase.
* BREAKING CHANGE: ApiQuery::newGenerator() and executeGeneratorModule() were deleted.
Change-Id: I7a3d7b6eb015d21ec1a9b9d9c6af9d97663f3f9a
|
|
|
|
| |
Change-Id: I8010fed6e138ee5b1803b9c5c0e678da3f2db9ef
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Only way to avoid messing with wrong request contexts.
Had to add recursion guard too.
Change-Id: Idc11b54752450321e01d92004e08fc95fb6170e6
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These hooks allow you to prepend, append or replace the search results
in Special:Search.
SpecialSearchResultsPrepend is executed immediately before the results
HTML begin to output. It can be used to include an external search
provider like Google CSE, for example. If the hook returns true, the
MediaWiki search results continue to output. If returned false, they
are suppressed.
SpecialSearchResultsAppend is executed immediately after the last
results HTML (including search navigation) are output. This hook is of
limited use since it will not be run in certain circumstances (there are
several points in the previous output logic where the function returns),
but is included for completeness.
Change-Id: Ib38433141979de999cdcab5eca26ba5416331aaa
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
- will update LiquidThreads accordingly and do not see
this hook used in any other extension in Wikimedia git repos.
Change-Id: Ib8f297b39dbd5fba980bb0d4773d0e01f2b922f4
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I31e9608ed3cef09656dac6ce6079259585299cb1
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is part a the solution to bug 42064: it modifies the EditFilterMergedContent hook
to allow it to be triggered by code outside the EditPage. This is useful when extensions
such as Wikibase implement their own editing mechanism for non-textual content.
Allowing EditFilterMergedContent to be used on non-textual content ensures that
any filters will also be applied to that content.
Note that EditFilterMergedContent was introduced in 1.21 which hasn't been released yet,
so modifying the hooks definition should not be a problem. The only extension that appears
to use the EditFilterMergedContent hook is Translate. I'll supply a patch.
To completely fix bug 42064, I will soon submit two changes to two extensions:
* In the Wikibase extension, trigger the EditFilterMergedContent when changing data
entities.
* In AbuseFilter, make use of the EditFilterMergedContent hook, so filters will also be
applied to non-textual content.
The the dicsussion on bugzilla for the rationale of this architecture.
Change-Id: I99a19c93e99860a91d7f898b0a3fbb72b69baab8
|
| |/
|/|
| |
| |
| |
| | |
Hook does not exist (anymore). Some background in bug 32925.
Change-Id: I830abd60f559cdd276458447f8f4c772b2d136b1
|
| |
| |
| |
| |
| |
| |
| |
| | |
Follow-up to If43cafb5. Almost complete. Needs another scan.
Added TODO where work is needed. I'll create documentation bugs for these
after the last scan.
Change-Id: I16a7bc03be71d1c907393c2a0748bf2150828bed
|
| |
| |
| |
| |
| |
| | |
Found using php maintenance/findHooks.php.
Change-Id: I6977cd5c57566025a63be1c5042d5d64eed44676
|
|/
|
|
|
|
|
| |
File formatting is very inconsistent. I updated approximately the first
part of the file.
Change-Id: If43cafb59828a1b846dd6dc751efc9ebcd7d5b72
|
|
|
|
|
|
| |
This will allow extensions to do some work based on the links inserted
Change-Id: Ia522de65ff17e28c6a8cd9997cf6225100fefc9e
|
|
|
|
|
|
|
|
|
|
| |
- maintenance/findhooks.php -> maintenance/findHooks.php
- ./maintenance/... -> php maintenance/... (*)
* Our maintenance files aren't released as executable, so this kind of
instruction could be confusing for UNIX system administration novices.
Change-Id: I5e1e76c46b3a8a4c7168c0b5715ede648044bd44
|
|
|
|
|
|
|
|
|
| |
- this enables an extension to do some processing on the RC line,
and if processing fails or for other reason, the extension has the
option to not output the line at all in Special:RecentChanges and
Special:Watchlist.
Change-Id: Ibf3a217afba5b4ad7992919399710fe3da301025
|
|
|
|
|
|
|
|
| |
Creating a new hook so that doubleunderscore (behaviour switch) magic
words can be defined from Extensions (so that I can solve bug 6754
from an extension rather than from core, as requested).
Change-Id: I734a4a1639be61052924838b19ed9db93a28e50b
|
|\ |
|