2016-07-22 18:59:10 +00:00
|
|
|
July, 2016
|
|
|
|
|
-----------
|
2016-07-27 21:00:05 +00:00
|
|
|
* BREAKING CHANGE: In the cross-wiki summary in ApiEchoNotifications,
|
|
|
|
|
'ts' is now ISO 8601.
|
2016-07-22 18:59:10 +00:00
|
|
|
* BREAKING CHANGE: JS variables: wgEchoSeenTime now uses ISO 8601, and
|
2016-07-27 18:46:55 +00:00
|
|
|
alert/notice instead of alert/message. wgEchoInitialNotifCount has
|
|
|
|
|
been removed.
|
2016-07-27 21:00:05 +00:00
|
|
|
* ApiEchoMarkSeen is moving to ISO 8601. Adjust your client; see API
|
|
|
|
|
documentation.
|
2016-07-22 18:59:10 +00:00
|
|
|
|
BREAKING CHANGE: Change $wgEchoDefaultNotificationTypes to be logical
Merge and deploy at the *same time* as:
* BounceHandler - I3c669945080d8e1f67880bd8a31af7f88a70904d
* mediawiki-config - I13817c139967ed9e230cfb0c87c5de66da793c96
Despite claiming to be about categories, $wgEchoDefaultNotificationTypes
was actually configuring both categories and types (which go inside
categories).
For example, 'thank-you-edit' is a type, but 'emailuser' is both
a category and a type (when used as a category, this has special
effects at Special:Preferences).
Since types and categories can and sometimes do have the same names,
this leaves no way to properly and clearly configure them. It also
makes it difficult to document what is going on (as required by
T132127).
Split into three variables:
$wgDefaultNotifyTypeAvailability - Applies unless overriden
$wgNotifyTypeAvailabilityByCategory - By category; this can be and is
displayed at Special:Preferences
$wgNotifyTypeAvailabilityByNotificationType - By type; this cannot
be displayed at Special:Preferences. To avoid confusing the user,
we introduce a restriction (which was previously followed in practice,
AFAICT) that types can only be overridden if the category is not
displayed in preferences.
Otherwise, it can look to the user like a category is on/off, but the
types within might have the opposite state.
Due to this configuration change, this is a breaking change, and needs
coordinated deployments.
This also lays the groundwork for T132127
Also change terminology to consistently use "notify type" for web/email.
It was mixing between that and output format (which unfortunately
sounds like the API format, e.g. 'model').
Bug: T132820
Bug: T132127
Change-Id: I09f39f5fc5f13f3253af9f7819bca81f1601da93
2016-04-19 02:54:15 +00:00
|
|
|
April, 2016
|
|
|
|
|
-----------
|
|
|
|
|
* BREAKING CHANGE: $wgEchoDefaultNotificationTypes has been split into
|
|
|
|
|
three variables. See Echo.php for documentation:
|
|
|
|
|
** $wgDefaultNotifyTypeAvailability
|
|
|
|
|
** $wgNotifyTypeAvailabilityByCategory
|
|
|
|
|
** $wgEchoNotifications[$notificationType]['notify-type-availability']
|
|
|
|
|
|
2015-03-16 15:47:13 +00:00
|
|
|
March, 2015
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
* Echo events now support multiple target pages. As a result The api output of individual
|
|
|
|
|
notifications within api.php?action=query&meta=notifications no longer has a 'targetpage'
|
|
|
|
|
property. This has been replaced with a 'targetpages' property which is the same as
|
|
|
|
|
'targetpage' was, but now as an array.
|