Errors when trying to post with rich text editor

Contribute Bug

AI-generated summary

Lisa_Nguyen reported issues with the new rich text composer, including unsaved changes, failed image uploads, and false “post can’t be empty” errors — particularly when pasting content from Gemini. sam suspected image optimization might be involved and asked for browser details. Lisa confirmed she was using Chrome 138.0.7204.157 (arm64) and found that stripping formatting before pasting resolved the issue. renato noted this shouldn’t occur and linked to a recent bug fix likely addressing the problem, requesting a minimal reproduction if it recurs. Lisa confirmed the issue appears resolved and thanked the team Lisa_Nguyen.

1

I’m not sure why but I haven’t been able to edit or create new topic with the new composer. Changes weren’t saved, images couldn’t be uploaded (it keeps saying “processing upload) and I kept getting errors “post can’t be empty” while it was not. Does anyone has the same issue?

Introducing our new composer, making writing on Discourse easier than ever
2

Yikes Lisa, this is certainly not expected, given the error it feels maybe related to image optimisation.

Which browser are you using (exact version?), Does this happen in other browsers?

Once we have this pin pointed we will be able to sort it out quickly.

1 Like
3

Hi Sam, thanks for your reply.

I’m using Chrome Version 138.0.7204.157 (Official Build) (arm64). I haven’t tried it on other browsers yet. After struggling with it for a few days, I realized this issue happened when I copied content from Gemini (which I used to help improve my writing) and pasted in the composer. Perhaps the formatting from Gemini messed something up, causing all of the issues I mentioned in my previous post. This didn’t happen with the previous composer version.

When I pasted the text from Gemini to another text editor first and removed more all the formatting before pasting it on Discourse composer, there was no issue.

1 Like
4

This should not happen in general, so if you face this again and can share a minimal example that triggers the error, that will help a lot.

There was a bug fixed today that is very likely to be the same you encountered, but please let us know if that happens again.

3 Likes
5

The bug seems to be resolved indeed. I’ll let you know if it happens again. Thank you!

2 Likes