On 10/24/23 18:53, Mark Sapiro wrote:
On October 24, 2023 3:47:10 PM PDT, Thomas Ward via Mailman-users <mailman-users@mailman3.org> wrote:
On 10/24/23 18:29, Mark Sapiro wrote:
What if you try this with
mailman-web shell?Doesn't error on load, but can't access configs in order to see if my custom handler is present. Which Abhilash said has to be done in the mailman shell - as does the documentation. Mailman can't even start with this added. Which is a problem.
I was confused. I should have said
mailman shell, notmailman-web shell.
Insert "circular problem" here.
When I DO NOT have the module loaded in the configuration, mailman shell works. Since that was functional, I went into the shell and
executed this:
from mailman_customizations.hooks import MailmanCustomizations
This worked fine, but obviously importing the class doesn't necessarily *activate* the class. So something is up with how I'm *supposed* to activate the plugin in the config, and we know that it's visible to Mailman in its shell, but it can't autoload it.
So, again, not sure where to look next for debugging.
Thomas