Closed matteocontrini closed 5 years ago
@matteocontrini could you possibly test whether this persists in dev-master?
I can confirm it's fixed
Still happening, according to Sentry: https://sentry.io/organizations/flarum-foundation/issues/1102576242/?project=1498784&query=is%3Aunresolved.
Shouldn't this just be $post->content
instead of $post->getContent()
? (The accessor is $post->getContentAttribute()
, but that is not meant to be called directly.)
I'll check today. The extension might not have updated.
Pretty sure that the next failure will be about the **set**Content()
call. :wink:
🤐 Correct.
When renaming a discussion, I'm seeing he following exception logged. The discussion is renamed, but the API request returns 500 and the user is shown an error.
It happens only with a particular discussion (or maybe others as well, but not all), and only after updating to beta8.
The exception seems to refer to something happening in this extension, although the discussion having the issue is not a discussion that was generated with a split. Some messages inside it were split to new discussions though.
Flarum info: