(Damn Phorge that auto-claims also for wontfix)

Maybe we can wontfix this. The current "workaround" D25485 by @waldyrious is just great and effectively fixed the super-confusing root problem.

This project is now abandonware without you. 😆

Gents, you’re both nothing short of geniuses

Gents, you’re both nothing short of geniuses—fixed before I’d even blinked! Thanks. Will look at fixing it permanently in T15513.

Fix was reverted for now as it had bad side effects.

I can reproduce, looks like the change in src/applications/conpherence/controller/ConpherenceViewController.php is the culprit.
No clue what's a correct fix, thus proposing to revert the entire commit.

Eventually please try reverting this change in your local copy:

Tip: activate DarkConsole and check requests there 👍

From checking the network requests when I load an unrelated page and the dialog appears, I can see a POST request to /conpherence/edit/1/ which returns the dialog. I've attached both the request and the response, with light redactions, to P48 and P49.

That's a good question. In general in Phorge/Phabricator any archived thing is editable. So I would say no, that archiving a chat still allows to write a message. But maybe it should not generate notifications.

Would sending messages be pevented on archived rooms and would all participants be removed (unless Can Edit is set to Room Participants)?

In T15237#14300, @valerio.bozzolan wrote:

I think a dedicated policy for "Can send messages" would be better, to cover more cases. It would be strange that all participants must also be allowed to edit all settings.