Error 500 when activating plugins (asset not found in the load path.)

[RGJ (Richard - Communiteq)]

@sistason

some old community plugins failing would lead me to believe them being too old

We are using these plugins for some of our clients. They definitely work on 2026.1.1.

@Jagster

My bet is translator plugin is eithet broken

Same: the translator plugin works on 2026.1.1.

@sistason

I did mount a docker volume to the plugins-directory (- plugins:/var/www/discourse/plugins)

I wouldn’t rule this out as a cause.