Louis Laugesen

> Just noting that we fixed a somehow-related issue with https://github.com/Automattic/jetpack/pull/39010 Confirming this isn't related to the other issue https://github.com/Automattic/wp-calypso/issues/91796, I don't think it could be related to this issue...

I'm not sure what the next steps here are but someone could timebox taking a look at trying to replicate the site state that leads to this. As a first...

Posted in dotcom-escalations, p1724126661488059-slack-C02FMH4G8

Reproducing _something_ consistently with these steps: - Open a post https://wordpress.com/post/ new / existing doesn't matter - Click the components dropdown menu icon (three dots to the right of help...

Looks like multiple issues but maybe they're related? > Here is the issue before: https://github.com/Automattic/wp-calypso/issues/59794 There was a follow up on that: https://github.com/Automattic/wp-calypso/pull/83474 And an open bug for a related...

I'm sure there is a much better way to do this but https://github.com/Automattic/wp-calypso/pull/93848/ seems to do the job. EOD here, will continue monday unless someone else can pick this up.

https://github.com/Automattic/wp-calypso/pull/93848 has fixed https://github.com/Automattic/wp-calypso/issues/83472 but this is unrelated to what is being reported above... back to looking for a way to repro.

Working theory: nonce verification failure. Need to move off this for the time being, please ping me directly if you find a new report of this.

@Automattic/zenith fyi while you're looking at untangling site users.

Reprioritizing normal as there doesn't seem to be many user reports and this doesn't seem to have a large impact on ux - confusing maybe, but not particularly broken.