Page MenuHomePhabricator

As a MediaWiki.org admin or Newsletter publisher, I cannot manage my own newsletter
Closed, ResolvedPublic

Description

This is strange. I have created two almost identical newsletters in test.wikipedia and MediaWiki.org. When I click "Manage", it works on test.wikipedia, but not in MW.o. I believe I have the same permissions in both wikis (administrator and publisher of that newsletter).

Both pages look the same, as an admin/publisher I see the same buttons. However, clicking "Manage", in MW.o I stay in the same page.

Introducing the URL manually, I also end up in the same page:

Event Timeline

I wonder whether it has to do with database permissions. A cannot open/update database kind of thing.

Clicking on "Announce", I do land in https://www.mediawiki.org/wiki/Special:Newsletter/1/announce. And the announcements work. I just sent a Hello World! one (with the secret intention of testing).

It looks like this is something to do with some interaction between the TwoColConflict extension and Newsletter

The onCustomEditor hook in TwoColConflict returns false when the TwoColConflict extension is enabled and the user is using the feature.
As a result the onCustomEditor hook for Newsletter is never fired.

In the short-term I'd recommend reverting my commit (https://gerrit.wikimedia.org/r/#/c/329202), which was just supposed to be cleanup and not have any actual effects. Long term we should probably refactor EditPage and make the edit conflict handling pluggable or something, so it doesn't require overriding the whole page (composition not inheritance).

Change 377308 had a related patch set uploaded (by Addshore; owner: Addshore):
[mediawiki/extensions/TwoColConflict@master] Revert "Don't mess around with $wgHooks by using CustomEditor hook"

https://gerrit.wikimedia.org/r/377308

Change 377308 merged by jenkins-bot:
[mediawiki/extensions/TwoColConflict@master] Revert "Don't mess around with $wgHooks by using CustomEditor hook"

https://gerrit.wikimedia.org/r/377308

Looks like the issue is now fixed and will be deployed with the next train!