> Actually, it assumes whatever the default is which might be
> http://localhost:8000. See
> https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/settings/mailman.py?ref_type=heads#L16
This is just tossing out some ideas, and it may not be worth it, but in the
code instead of hardcodi
On 6/19/25 14:30, Sam Darwin via Mailman-users wrote:
Thanks. That fixed it.
Comments:
1. In the docs, the instructions say "POSTORIUS_TEMPLATE_BASE_URL =
'http://localhost:8000'. As a reader, you are thinking, I'm running both hyperkitty
and postorius. Hyperkitty is at /archives/ and postori
On 6/19/25 15:42, Sam Darwin via Mailman-users wrote:
It takes time to figure out a new feature. I see what is happening. :-) Or,
merely one step further.
After a template is stored in the DB you can remove POSTORIUS_TEMPLATE_BASE_URL
because the value is cached in the DB. That explains the
It takes time to figure out a new feature. I see what is happening. :-) Or,
merely one step further.
After a template is stored in the DB you can remove POSTORIUS_TEMPLATE_BASE_URL
because the value is cached in the DB. That explains the caching.
Next, without POSTORIUS_TEMPLATE_BASE_URL,
Thanks. That fixed it.
Comments:
1. In the docs, the instructions say "POSTORIUS_TEMPLATE_BASE_URL =
'http://localhost:8000'. As a reader, you are thinking, I'm running both
hyperkitty and postorius. Hyperkitty is at /archives/ and postorius is at
/mailman3/ . What about the path '/mailman3/
On 6/19/25 12:06, Sam Darwin via Mailman-users wrote:
It seems templates can be configured in the filesystem or via postorius. When I
place a footer template in the filesystem it worked fine. Then without
adjusting any configuration, without removing that, I tried to use the
postorius control
