Open lizadaly opened 1 year ago
I was eventually able to to reproduce this, but I don't think it's fixable because it's a side effect of the H2O draft/revision model. We could probably catch the error differently, though explaining what to do next would be complicated.
What happened here is that the user created a draft, worked on it, and then accidentally went back to the published version, clicked "publish", and got (behind the scenes) a permission error because the backend claimed that it wasn't able to transition between the state of published and published.
The user thinks they were able to fix it by changing the description field, but that's just because they probably got back to the correct draft URL in doing so.
Reported by a user: