Toggling property conversation.metadataArchiving should not require a restart
#142
Comments
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Dec 11, 2020
…change The property 'conversation.metadataArchiving' controls wether the plugin is considered 'enabled'. A restart of the plugin shouldn't be required for a change to the value of that property to become effective.
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Dec 11, 2020
…change The property 'conversation.metadataArchiving' controls wether the plugin is considered 'enabled'. A restart of the plugin shouldn't be required for a change to the value of that property to become effective.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The property
conversation.metadataArchivingcontrols wether or not (some features of) the Monitoring plugin are enabled. This setting can be toggled (either manually, or though the admin console pages provided by the plugin), but this change does not take effect immediately. There's no reason why it could not be.The text was updated successfully, but these errors were encountered: