#1633 plugin_paths in config file will not be considered
Reporter
SadButTrue
Owner
Nobody
Created
Updated
Stars
★ (1)
Tags
Priority-Medium
Status-Invalid
Type-Defect
SadButTrue
on
What steps will reproduce the problem?
1. Install Prosody Community Modules
2. Set "plugin_paths" in Config to the directory of Prosody Community Modules
2. Update to Prosody 0.11.8
3. Restart and watch Prosody's logfile(s)
What is the expected output?
Plugins should be loaded from the given directory
What do you see instead?
Example:
modulemanager error Unable to load module 'cloud_notify': /usr/lib/prosody/modules/mod_cloud_notify.lua: No such file or directory
What version of the product are you using? On what operating system?
Prosody 0.11.8 on Debian 10
SadButTrue
on
Sorry for any confusion - pls. delete this report.
My problem came about because I installed Jitsi Meet. In the config file ( /etc/prosody/prosody.conf.lua ) it seems that the path for the plugins is not taken into account.
If you change the plugin path in the Jitsi Meet Config ( /etc/prosody/conf.d/your.jitsi-meet.conf.lua ) the community modules are loaded again.
But this is strange.
Zash
on
Yeah, only the last plugin_paths setting seen during config parsing has any effect.
What steps will reproduce the problem? 1. Install Prosody Community Modules 2. Set "plugin_paths" in Config to the directory of Prosody Community Modules 2. Update to Prosody 0.11.8 3. Restart and watch Prosody's logfile(s) What is the expected output? Plugins should be loaded from the given directory What do you see instead? Example: modulemanager error Unable to load module 'cloud_notify': /usr/lib/prosody/modules/mod_cloud_notify.lua: No such file or directory What version of the product are you using? On what operating system? Prosody 0.11.8 on Debian 10
Sorry for any confusion - pls. delete this report. My problem came about because I installed Jitsi Meet. In the config file ( /etc/prosody/prosody.conf.lua ) it seems that the path for the plugins is not taken into account. If you change the plugin path in the Jitsi Meet Config ( /etc/prosody/conf.d/your.jitsi-meet.conf.lua ) the community modules are loaded again. But this is strange.
Yeah, only the last plugin_paths setting seen during config parsing has any effect.
Changes