Part of the PageTriage functionality is to post to user talk pages is some cases. Currently, if Flow is used for those, this gives:
error: {
code:"appendnotsupported"
info:"Can't append to pages using content model flow-board"
*:"See http://127.0.0.1:8080/w/api.php for API usage"
}The solution is to use MessagePoster.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add MessagePoster/Flow support to PageTriage, fix related issues | mediawiki/extensions/PageTriage | master | +527 -411 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Mattflaschen-WMF | T85030 Add Flow support to PageTriage using MessagePoster | |||
| Open | None | T123522 Implement a server-side mw.MessagePoster equivalent |
Either PageTriage could be made Flow-aware, or Flow could support action=edit&appendtext=wiki+text. The latter is T85197
Currently, it's using appendtext. But I don't think we want to use that for Flow. See my comment at T85197: Flow API: Let code append to the board header with action=edit&appendtext.
One solution is to switch to creating a new section (section=new), then make this depend on T59989: S2. Flow API: Let code add a new topic with action=edit§ion=new. If they're not using Flow, section=new should still be suitable (e.g. some bot notifications use a section per notification, e.g. https://en.wikipedia.org/w/index.php?title=User_talk:Superm401&oldid=639672099#Disambiguation_link_notification_for_October_16).
Actually, I think it only needs the client. Before, I may have misread ApiPageTriageTagging, and missed that appendtext was being used on the article, not a talk page.
Change 311856 had a related patch set uploaded (by Mattflaschen):
Add MessagePoster/Flow support to PageTriage, fix related issues
Change 311856 merged by jenkins-bot:
Add MessagePoster/Flow support to PageTriage, fix related issues