Closed ArchBlood closed 2 years ago
I can't replicate this on our translation server. Are there any specific steps to reproduce the problem?
Not exactly sure, all I did was enable the module while having custom modules with custom namespaces, example being the scroll up module and a few others from @GreenMeteor 🤔
Strange, so this does not affect our translation community?
Doesn't look like it affect the translation site unless the translation site also use custom modules with custom namespaces?
namespace gm\humhub\modules\scrollup
Hmm just tested it, and the scrollup modules works fine with a custom namespace.
I've disabled and re-enabled the module some of the options have come back but not all are available still. :thinking:
Although once I try updating the translation it throws the same error... :disappointed:
Hmm I cannot reproduce this with the "scrollup" module on my local environment
I could not recreate the broken core modules as in your screenshot, but I probably found the problem with your custom modules. Currently the directory name of your module needs to match the module id. So it does not work if your module directory name is e.g. humhub-modules-scrollup
it needs to be scrollup
.
Regarding the broken core modules, are there maybe any other errors hidden in the logs?
I did also run php yii message/extract-module scrollup
I only got the scrollup module translation working when changing the namespace but got most of core working again, as for error logs didn't show any @buddh4
Would seem that now most translations are broken and only show
%
this also affects custom modules that have translatable filesThrows this on trying, no error logs