Discourse Plugin Compability?

[robi]

@IniBudi I run NodeBB just like this Cloudron forum here, which may be a better option for you.

[girish]

Discourse is getting there. I have managed to get the app updated. Now it's just a lot of testing.

[jdaviescoates]

@girish great, thanks!

[girish]

Latest package should have plugins working again.

[IniBudi]

@girish confirmed it works! Thank you for your support!

[IniBudi]

I already tested the below plugins and it's compatible with Cloudron

https://github.com/discourse/discourse-staff-alias https://github.com/discourse/discourse-solved https://github.com/discourse/discourse-chat-integration https://github.com/discourse/discourse-automation https://github.com/discourse/discourse-follow https://github.com/discourse/discourse-yearly-review https://github.com/discourse/discourse-zoom https://github.com/discourse/discourse-oauth2-basic https://github.com/discourse/discourse-cakeday https://github.com/discourse/discourse-topic-voting https://github.com/discourse/discourse-translator https://github.com/discourse/discourse-bcc https://github.com/discourse/discourse-assign https://github.com/discourse/discourse-bbcode https://github.com/discourse/discourse-signatures https://github.com/discourse/discourse-encrypt
https://github.com/discourse/discourse-user-notes
https://github.com/discourse/discourse-teambuild

The below plugins are not compatible with Cloudron

https://github.com/discourse/discourse-ai https://github.com/discourse/discourse-prometheus

[nafets-lesierk]

Wouldn't we need to update to something?
My Cloudron installation says it is up to date with Discourse Cloudron version being org.discourse.cloudronapp@2.2.3 11.11.2023.
?

[nebulon]

Which version is your Cloudron at currently? The latest discourse release requires Cloudron 7.6.0

[nafets-lesierk]

I always fall into the same hole ;-(
Thanks

[nafets-lesierk]

Oh what a pain - netcup no AVX, I think I have to shoot myself .......

[jdaviescoates]

@nafets-lesierk thankfully it's really easy to move server with Cloudron.

I'd recommend moving to Hetzner - almost as cheap at Netcup, but overall much better imho

Follow the instructions here:
https://docs.cloudron.io/backups/#restore-cloudron

I recommend doing a dry run first.
https://docs.cloudron.io/backups/#dry-run

I'd also recommend checking the spam black list status of the IP (e.g. on here https://mxtoolbox.com/blacklists.aspx ) of your new server before starting to move over to it (and if it's bad as for a new IP/ new server that has a clean slate).

[jdaviescoates]

https://github.com/paviliondev/discourse-events doesn't seem to work

More info here:

https://forum.cloudron.io/post/82941

[nafets-lesierk]

Thank you very much, will look into it.
It's just - I hate the prospect of spending another minute with these back office things ... Oh well.

[marcusquinn]

@IniBudi said in Discourse Plugin Compability?:

https://github.com/discourse/discourse-subscriptions
https://github.com/discourse/discourse-reactions

Did you get these working?

[wrapper]

I'm also struggling to get discourse-reactions to work. It loads in but only seems to work on mobile for some reason

[andreasdueren]

@IniBudi said in Discourse Plugin Compability?:

https://github.com/discourse/discourse-translator

Are you still using this plugin? I can't get it to work. Installs but won't let me use my LibreTranslate instance (or more precisely there is no translate button on the frontend under a post)

[james]

Hello Cloudron Discourse Users.

Yesterday I took a look at the two plugins.

Reactions

This plugin is throwing a javascript console error:

Uncaught Error: Could not find module `ember-curry-component` imported from `discourse/plugins/discourse-reactions/discourse/components/discourse-reactions-actions`
    at loader.js:247:1
    at h (loader.js:258:1)
    at u.findDeps (loader.js:168:1)
    at h (loader.js:262:1)
    at u.findDeps (loader.js:168:1)
    at h (loader.js:262:1)
    at requireModule (loader.js:24:1)
    at k (chunk.b7e52c4e533794a939ae.d41d8cd9.js:1:327870)
    at T (chunk.b7e52c4e533794a939ae.d41d8cd9.js:1:328090)
    at chunk.b7e52c4e533794a939ae.d41d8cd9.js:1:327340
    at y.start (chunk.b7e52c4e533794a939ae.d41d8cd9.js:1:327506)
    at HTMLDocument.<anonymous> (start-app.js:5:7)
    at discourse-boot.js:13:12
    at discourse-boot.js:1:1

This might be the cause why it is not fully working.

Translator

This plugin is odd to say the least.
I had it working once with LibreTranslate hosted on the same Cloudron.
But this plugin works in some uncontrollable matter.
After hours of debugging why suddenly in the new installation the translation button is missing, I found the following.
This plugin determines when to show the button and when not my analyzing the currently viewed post / topic.
And if the topic is detected to be not the discourse users locale it should display the translation button.
But this sometimes work and sometimes not and there is no setting to just enable it everywhere.

[jdaviescoates]

@james said in Discourse Plugin Compability?:

But this sometimes work and sometimes not and there is no setting to just enable it everywhere.

I guess we should request a "please have it on everywhere as the logic isn't consistent and users often change or obscure their local in various ways" should be added upstream somewhere.

@james I'd LOVE it if you could also have a look at getting this Discourse Events plugin working on Cloudron too https://meta.discourse.org/t/events-plugin/69776

[james]

Hello @jdaviescoates
If there is time, I can check it out.
Also, the "user locale" is not the browser user locale but the discourse user locale.
By default, users in discourse can not even choose their locale and have to use the system-wide one.
And by default the system-wide default locale is en.
So if a post is created in German, it should work.
Should, is the keyword here.

[james]

FYI @discourse users:
After my work yesterday the discourse-reactions plugin was archived on GitHub.

This repository was archived by the owner on Jul 10, 2025. It is now read-only.

This plugin has now been bundled into Discourse core. See: https://meta.discourse.org/t/bundling-more-popular-plugins-with-discourse-core/373574

So best to uninstall the plugin.