The latter is deprecated, and the former is just a wrapper for
UserEditTracker::getUserEditCount().
Bug: T290521
Change-Id: Id3f2b9a007fe299d74d5957cbd3e31b11adb2790
EditAttemptStep and VisualEditorFeatureUse have this one very annoying
inconsistency.
Bug: T281409
Depends-On: I96e07e10943d330efcf47e0a2989ea3b73bae428
Change-Id: I3bddd3096625466fc5b6c88b64a570a389b87a05
Adds a hidden field to the edit page form, with JS that will set its
value. Server-side then checks for that value and logs whether it was
correctly set.
Bug: T263505
Change-Id: I8be06385aa6d97e5536cfc252d34297e1c000a32
Support the `url-new` mechanism so we can distinguish between
new/existing sections in direct navigation.
Bug: T272544
Change-Id: I2c431592035c7ccedbbe612bc97f63141fc4dab7
Depends-On: I3cee7a3a4c4b646692dce4a1180c4ba18a61f4bc
If someone is enrolled the DT a/b test, we want to know about their
editing here as well.
Bug: T273096
Change-Id: If2bb04011c8ca54e8c7ffd073e21bec45e92460c
In some languages, image options like 'alt' or 'thumb' can have
multiple synonyms. They were only handled for English (and were
hard-coded).
Change-Id: Ib03932d3d85a5540bea325f2717da3365756a90e
* Use the error code from the API for 'save_failure_message', instead
of the key of the localisation message shown to the user.
Although this editor is not using the API, and doesn't use those
error codes, we still want to use them in logging for consistency
with all the other editing tools.
We can easily generate the error codes from the Status we do have.
* Copy 'save_failure_type' map from VisualEditor.
Bug: T272162
Change-Id: Ia9eeea14e3d4a6a691f84628a27ffc0c3bf061c1
As noted by Jack Phoenix in I07b0e0e030217d74f06bb2b6fc278bd2e28e34b5
the core toolbar has not been present since 1.32 and this hook is
therefore rather pointless.
Change-Id: Ibcf4400237dbf3b195e2bc6a8efee9f1b1527e6d
The editingStatsId POST data parameter was already used to propagate the
session ID within a session; also allow it to be read on GET requests,
to allow the initial session ID to be overridden.
Similarly, propagate the oversampling state and allow it to be set in
the query string using ?editingStatsOversample=1 .
Bug: T238249
Change-Id: Ib4586607b4acb69bdfbd6a8de0f320b90969209a
This allows us to bundle the wgWikiEditorMagicWords and
mw.msg.wikiEditor(?!) config vars that were previously exported globally
in the startup module.
This code is old and crufty, so this is a somewhat minimal conversion:
* Use require() for jquery.wikiEditor.{dialogs,toolbar}.config.js,
and for jquery.wikiEditor.{dialogs,toolbar}.js
* Don't attempt to convert jquery.wikiEditor.js to something
require-based, instead just run it and let it set the $.wikiEditor and
$.fn.wikiEditor globals
* Consolidate ext.wikiEditor.{dialogs,toolbars}.js into
ext.wikiEditor.js
Bug: T222828
Change-Id: Ia75d685cbde786e8fceb6db36f2436b2beea1499
This is an internal variable that hasn't been used since 2017
with commit be36244c70. It was kept for back-compat with
regards to caching, which as churned long since.
Bug: T219342
Change-Id: I7c71956e34c1d4312037f9a8d26f81125ab82577
Use the new extension.json attribute instead.
Bug: T214211
Change-Id: I79c45c6923fd19f6f9f068492b3bd6548161dd04
Depends-On: I27ecebe27d7aaebe6d1317bc5eaea9cca368b45d
The schema itself is being renamed, and many of the field names are
different.
Bug: T207803
Depends-On: I2949c9782669b75cf17978698c8cef21fdee6dea
Change-Id: I07d9bc1530005914043911b7906c1602522c9162
Add the secondary label in a 'help' note to make it easier to identify
the different editors.
Bug: T32795
Change-Id: I6d17359166f58811ba99893ce4a4500a87deb827
Respect the config var exported by WikimediaEvents that, if set to true,
forces oversampling. When oversampling, all events are logged even if
they would have been sampled out. The isOversample property is set to
true if the event was oversampled and would not otherwise have been
logged.
Bug: T206543
Depends-On: I5fdf5fdd2dc0d99a0a0d7eb7ab2e3dce4798009b
Change-Id: I7e504884a888c4d080cd4762549b72489126ed65
Instead of hard-coding the 6.25% sampling rate, allow it to be
controlled by the config variable in the WikimediaEvents extension
(which also defines the RL module for the Edit schema).
Also use sampling code from EventLogging so we can configure the
sampling rate as a number, rather than using a hex-digit based strategy.
Bug: T206543
Depends-On: I00383cec62f6c2a0137b329565b0ca84bfbb223f
Depends-On: Ib746fc708e7b752cebc5fd8d080e40819dfa34f3
Change-Id: I2956efc9294768742dd49dcb36770f0509e4090f
