Glad it worked out in the end. It is probably not obvious also to use the credentials from the env variables which have IMAP in them....

Discourse has moved to a new release versioning model - https://meta.discourse.org/t/introducing-releases-discourse-org/392712 . We are moving the package to the new versioning .

Hello @phneutre On the right side of a topic is a button called Topic Tools there you can press Ask a question, then a topic will be marked as unsolved and can be marked as solved later on. I have done so. Always happy to help.

Thank you @james ! I'll maybe open an upstream issue for the missing images. I guess the expected behaviour would be that at least the emoji picker simply omits the images not present in the emoji folder. For existing posts, it's understandable that a broken image is shown.

Haven't been able to find a solution and just dealing with the notification of not using a CDN while using the S3 storage.

Fantastic - thank you, worked

@james update to v3.5 went fine and the personal queries from the data-explorer plugin where still in place. I now only get the notice [Admin Notice] Plugin 'discourse-translator' contains code which needs updating. (id:discourse.post-stream-widget-overrides) (learn more) And will have to find out again how to manually update a plugin.

@girish Thanks. Looking forward. Would it be possible to include my little request with the update ? c.f. https://forum.cloudron.io/post/111958

For future users, there is documentation here - https://docs.cloudron.io/packages/discourse/

3.5 is stable now and brings lot's of new features...

@matt-derrick gosu cloudron:cloudron bundle exec script/rails console does not give a rails console? (from your screenshot it does seem like that) . It just hangs is it? It works fine here on my cloudron too. You can try this on the demo cloudron to see how it is supposed to work . https://my.demo.cloudron.io (username/password is cloudron)

Unfortunately I can't tell you preciesly. Once, I did reset the all the users preferences via the console: https://meta.discourse.org/t/reset-default-categories-watching-setting/244930/8 But there was no error message in the dashboard. Otherwise, I didn't do anything of importance. For updates, I think the error message appeared not before 3.4.3 or 3.4.4… Sorry for the vagueness.

Was fixed, is working.

Works on a fresh instal atleast. [image: 1747991044489-9e1fee30-4e00-40af-a521-049548b79e66-image-resized.png]

@bmann I will take care of this and make sure your advanced guide will be added to https://docs.cloudron.io/apps/discourse/#incoming-email-setup Thanks for the already done write-up!

@wrapper this is quite an old issue. Can you create a new post with whatever issue you are facing?

Just to close this topic. With some help of the discourse AI on ask.discourse.com, I could solve the problem. It was not a bug but an entanglement of site settings and user preferences due to the modifications made over time. Solution: https://meta.discourse.org/t/reset-default-categories-watching-setting/244930/8

@joseph Perfect, thank you ! That did the job. And to my surprise, the settings (LibreTranslate API and URL) were still in place !

Confirming that Discourse backup worked properly after updating the app to pick up the 5.0.0 image. Thank you!