It can still use this module for pre MediaWiki 1.24 installs (if desired) but when installed in current MediaWiki it should use csrf tokens.
Relevant:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Clean up token handling | mediawiki/extensions/Translate | master | +80 -265 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T46602 Require POST for all changes; Never change content on HEAD-request | |||
| Duplicate | Krinkle | T33270 Proper AJAX rollback functionality in core | |||
| Duplicate | None | T49782 Rollback workflow needs further thought | |||
| Stalled | None | T88044 Make rollback use POST instead of GET (use AJAX in GUI) | |||
| Resolved | Krinkle | T72059 Update mediawiki.api for new API token handling | |||
| Resolved | Nikerabbit | T117797 Translate extension should not depend on deprecated ApiTokens module |
With 42e9a653090288d9b57225130c206a0559325131 landed, the old interface now supports csrf as well so that Translate can migrate without having a circular dependency on MediaWiki core migrating to the new interface first.
I don't see how that helps me. I used edit as alias for csrf for now while getting rid of the old custom token types.
Change 251697 had a related patch set uploaded (by Nikerabbit):
Clean up token handling
That's fine too. I thought you would want to use "csrf" directly in getToken(), which didn't work in the past because it only existed in the new API.