| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/
| |
| |
| |
| |
| |
| |
| | |
Reorganization of active, blocked, and suppressed block log table's columns
Bug: T387714
Bug: T387399
Change-Id: I9c7729e9adaf041b0d8d0643d01c5f957f6b1862
|
|/
|
|
| |
Change-Id: I28abfab76b1c7dfa268e7ea2a8c0c50672e87bda
|
|
|
|
| |
Change-Id: I8984f7f0ca175a3d840442e66817d4adcaafcf9f
|
|
|
|
| |
Change-Id: Ice1b0bef4d9a0162fcd513410aa31d73deb1ec63
|
|
|
|
| |
Change-Id: Ic3ae91fc65e12841f477d19232e1ed8ad265f291
|
|
|
|
|
| |
Bug: T387468
Change-Id: Id0dedd5f04f97ac6b23ec0856283b2a0fb946bad
|
|
|
|
| |
Change-Id: I90524d58aabe8ad16e4c53e2a3910c99d0fd05a8
|
|
|
|
| |
Change-Id: I357515aef92ea5e98a578a1610113e61785e583a
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Factor out LogEventsList::getBlockLogWarningBox()
* When the user is blocked multiple times, add Special:BlockList link
Bug: T384916
Change-Id: I4d538ab59e55dc96dde5dd00dd8016c028bfe6d0
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Why:
- We would like to make the user links associated with expired temporary
accounts visually distinguishable from non-expired ones using
strikethrough styling and an information tooltip.
- The designs call for using Codex tooltips for the latter. Using the
Vue directive for this would require us to take a dependency on Codex
and Vue for every page that renders user links, and render a small
Vue.js app for each expired temporary user link, which does not seem
practical.
- We can, however, use Codex styles and implement our own simple tooltip
functionality without taking on unnecessary dependencies.
- This requires adding a new RL module to every page that uses
userLink(), so we should update userLink() to do this for us instead
of having to update every core and extension page that needs this.
What:
- Add a strikethrough to expired temporary account links
as per the design specification.
- Render a tooltip, hidden by default, for expired temporary account
links that is styled using Codex styles.
- Implement a simple jQuery tooltip handler for expired temporary
account links.
- Avoid caching expired temporary account link in UserLinkRenderer to
ensure each of them receives a unique ID.
- Add required ResourceLoader modules directly to the output in
userLink().
Bug: T358469
Change-Id: I4f70ff15becbc4991c4f1b0307a14d5354c79dc1
|
| |
| |
| |
| | |
Change-Id: I69472adef5c1d04c7c28679f7c48371f07372f94
|
| |
| |
| |
| | |
Change-Id: Id3e5ba20513bcad9b6325503116e35381c3cc6f6
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of special-casing it in EditPage and in ApiEditPage,
PageSizeConstraint sets the error message itself.
Add some notes about T384399. I hope this change can serve as an
example for further work on that task.
Other changes:
* Do not show the error on editor load, only on edit form submission.
The error on load was added in 2006 when the maximum page size was
first limited (aa2bde93 / SVN r13070), and should not be needed any
more now that there shouldn't be any pages exceeding the limit in
the database any more. In case there are, the user will still get
the message when they try to save an edit.
* Streamline the message (there's no need for emphasis in the message,
since it's shown in a very prominent error box these days).
* Use the same message in API errors. Preserve the API error code for
compatibility.
* Alphabetically sort some arrays and switch cases.
Bug: T384399
Change-Id: I0892d1189e29013b9ff4325c8017bab524b84b7e
|
| | |
| | |
| | |
| | | |
Change-Id: I34fd825cb958633503af513192f60721721ec5e8
|
| |/
|/|
| |
| |
| |
| |
| | |
It is not clear who the "brand-new users" are in this case so help-message is required here.
Bug: T381205
Change-Id: Idfc1b7e4b5b1686f0edf69b32e0d4152b30e54ae
|
|/
|
|
| |
Change-Id: I931414884e79d78363c8694a4d0aee77550e9c30
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Why:
* Temporary accounts are automatically created when a user makes
an edit, and therefore do not have a password set by the user
who created the temporary account
* Currently, there is no limitation that prevents a password being
set for a temporary account.
** This means that the createAndPromote.php maintenance script
can set a password for a temporary account or create a new
temporary account with a specified password.
* A temporary account having a password allows a user to login to
the account, even after the account has expired.
** This should not be allowed, and as such we should reject any
attempts to set or change the password for a temporary
account.
What:
* Update User::checkPasswordValidity to reject any password
provided if the user matches the temporary account name format.
* Add tests for this.
Bug: T386775
Change-Id: I5354d240678fca9dbf3ed699370cf1a4df96b2f9
|
| |
| |
| |
| | |
Change-Id: Id17dc2a8d468370ee5398586783103c0df0e6bf5
|
|/
|
|
|
|
|
|
| |
Option 3 from the task. Show one log entry but vary the introductory
message. Include the total number of blocks in the message.
Bug: T384916
Change-Id: I15fa1f77a38579ed5677f9f156d1667762dc645b
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Add cancel button that closes and clears the form.
Bug: T384828
Change-Id: I24886a21951e1f7472e6b784878124fe812299eb
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Removed split hak.json L10n-bot didn't remove moved messages in master branch for unknown reason.
Fixed attribution.
Manually exported using https://translatewiki.net/wiki/Special:ExportTranslations .
Bug: T371883
Change-Id: Icdede1f2aaffb04ebd8c208f5c9bcd8dd0232c50
|
| |
| |
| |
| | |
Change-Id: I18488de894004ccb9a47a35b454bab0e5ef948cd
|
| |
| |
| |
| | |
Change-Id: If5c6fb2b3f5a1d6b8d42268305018ff56ea2ed29
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Nothing else in qqq.json describes a link to mediawiki.org with
code. Describe the link by allowing the translator to easily open
said page and click on it, by making it an actual link.
The term for the left part of a wikitext link is "link target".
Bug: T384678
Change-Id: I716be0e64e927d6bb17c902a7a06e28868978399
|
| |
| |
| |
| | |
Change-Id: Ia72373ae6cfd072f3cc9dd2158d620aaaab760f1
|
|/
|
|
| |
Change-Id: Ib3a6f4867ed8c51f1e252cd59a8d5bcd21200efa
|
|
|
|
| |
Change-Id: Ice547875e98b2fa2b0ae1594a531a38b2f738ade
|
|
|
|
| |
Change-Id: Ieda8d483df6c85d6c766414f2e9602f94b9dc85e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RenameUserJob is moved to Job/RenameUserTableJob because there are two kinds of jobs now.
The newly added RenameUserDerivedJob is used for performing user-renames across
a wiki family using virtual domains or shared tables. Most code are
moved from SpecialRenameUser and maintenance/renameUser.
The new service, RenameUserFactory is added for constructing RenameUser
easier.
When a global rename happen, the central wiki will enqueue
RenameUserDerivedJobs for other wikis in the same family.
The derived jobs will check if the central wiki has the same user table
as local, and perform updates to local tables.
A new user-right 'renameuser-global' is also added because wiki families may
want global users to be renamed only by a limit set of users or
on a certain global wiki.
Bug: T104830
Change-Id: Ic4120cbd9a4850dfe22d009daa171199fe7c5e39
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Drop colons after words like "granted", "revoked", not to have awkward
double colon. Rephrased "kept without changes", to "kept $1 unchanged"
to align better with English grammar.
Bug: T369466
Change-Id: I059a6dc3934274d6e809033d6a5230445cf33ab8
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Bug: T167762
Change-Id: Ief367df383938375fc9965af42d5b575e89eb210
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
Bug: T384678
Change-Id: Ifb048489d24cda51ff62b64c0ff21b87eaec2580
Follows-up: I20a3fe8484424427de5dcc55098a09114fedaf66
|
| |
| |
| |
| | |
Change-Id: I5c69db1774f3659b213467e3a238c02a8286f9a8
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, the log displayed a list of former groups and a list of new
groups, which wasn't particularly helpful when user had a ton of groups.
Now, the log message is split into four parts: added groups, removed
groups, changed expiration, and groups kept intact.
This style of presentation highlights what has changed but still allows
user to reconstruct the whole set of groups before or after the change
was made (as it was possible before this patch).
Bug: T369466
Change-Id: I80d22ef7cbdc60a1437e26b6f9a6ee11bbecab64
|
|/ /
| |
| |
| | |
Change-Id: Ie305a422133d22a277a432462aa566dd3a876c9b
|
| |
| |
| |
| | |
Change-Id: I5495becb444413be27e0f2831adddaf5696834a3
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Parsing {{PLURAL}} seems broken for unclear reasons
(see T306326). As a workaround, removing {{PLURAL}}
entirely and replacing it with the abbreviation "sec.",
which doesn't need pluralization.
(There's no need to change qqq, because I already
updated it in translatewiki.)
Bug: T306326
Change-Id: Ia7e2cd4f75cf1cd8ca78b38844c932dfdd4a7ea4
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make the link be in the Navigation sidebar (as the last link) by default by changing the default "sidebar" interface message and adding a new "specialpages-url" interface message. If an existing navigation does not contain the "n-specialpages" item, we append it to the end of navigation. As mentioned in the task, this is done to line up with the other links in the main menu (navigation) vs the toolbox.
As that sidebar is specified through the "sidebar" interface message, the only way to add the link to the main menu without setting great new precedent is to change the default interface message.
In accordance with existing links in the default sidebar, the link to "Special pages" was specified through a URL interface message formatted the same way as the "Recent changes" entry.
The "createSidebarItem" function executes code shared between the addition of n-specialpages and the addition of other sidebar items. Hopefully I got the naming part and the getting-config-and-services part right.
This approach requires some user notice, as users should update their MediaWiki:Sidebar to include n-specialpages. I also wonder about the performance footprint, especially that of foreaching the sidebar to find n-specialpages and that of copying over config, services, etc. every time a sidebar item is generated.
Bug: T333211
Change-Id: I03f818d414c605a3cc87dfd108a8860a09d41d5f
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: If0bb526f5e1dfb6f86e494f6913959ce5aa20ac6
|