Page MenuHomeMiraheze

Structured Discussion boards not creating in many wikis
Closed, ResolvedPublic

Description

On many wikis, Structured Discussion board creations fail with "Flow\Exception\NoParserException". Examples are greatcharacterswikiwiki and cancelledmovieswiki.

Event Timeline

Redmin triaged this task as Normal priority.Apr 6 2021, 15:20
Redmin claimed this task.
Redmin added a project: Upstream.

This appears to be an upstream issue.

We really need to get this fixed as soon as possible.

Redmin reopened this task as Open.EditedApr 6 2021, 15:56

Any Sysadmin able to do a trace to see what is causing the exception? This was never so severe, as far as I am aware. It could be a different issue this time.

Redmin removed Redmin as the assignee of this task.Apr 6 2021, 15:57
Redmin raised the priority of this task from Normal to High.
Redmin added a project: Production Error.
Unknown Object (User) subscribed.Apr 6 2021, 16:19

This is Upstream. Unless... there is one possibility that this is a local issue, if you don't have the writeapi right then it might cause this.

Herald removed a subscriber: Unknown Object (User). · View Herald TranscriptApr 6 2021, 16:19
Dmehus added a subscriber: Unknown Object (User).EditedApr 6 2021, 16:25

This is Upstream. Unless... there is one possibility that this is a local issue, if you don't have the writeapi right then it might cause this.

@Universal_Omega They do have writeapi as part of their founder, sysop, and user groups, so that doesn't appear to be an issue, unless maybe since Flow talk page manager isn't a real user, it would need writeapi as part of the * group? I'll test that theory.

Herald removed a subscriber: Unknown Object (User). · View Herald TranscriptApr 6 2021, 16:25
Unknown Object (User) added a comment.EditedApr 6 2021, 16:30
In T7099#140715, @R4356th wrote:

Any Sysadmin able to do a trace to see what is causing the exception? This was never so severe, as far as I am aware. It could be a different issue this time.

T6780#136602 was the trace I ran on this when I was still a sysadmin, and provided this is the same error. But the trace would be the same even if not same cause since it's the same exception.

Dmehus claimed this task.
Dmehus added a subscriber: Unknown Object (User).

This is Upstream. Unless... there is one possibility that this is a local issue, if you don't have the writeapi right then it might cause this.

Per my comments above, I've tested my theory here, and this seems to be the case.

@MarioMario456, you will need to either keep writeapi in the * group, or you may be able to add it to the bot or flow-bot user group. I've not tested it with either of those groups.

Herald removed a subscriber: Unknown Object (User). · View Herald TranscriptApr 6 2021, 16:31