On 13/2/21 11:55, Victoriano Giralt wrote:
On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote:
If the manage.py in the directory in which you ran this is the correct one for your Mailman Django project, I don't know why it didn't work. Me neither :-( That's why I asked, and probably Guillermo, as well.
Is your Mailman installed in a virtualenv? If so, was the virtualenv activated? No virtualenv. Mine is deployed using system python on a CentOS 7 system, toghether with another in house developed low requirements Django project, both served by uWSGI vassals.
And mine, as well, in a FreeBSD 12.2-RELEASE, no virtualenv and uWSGI approach with apache24 server.
And then, all of a sudden, while I was writting this, it dawned on me!
Postorius, Hyperkitty and django-mailman are installed with pip, so, the end up in the site-packages directory (usually /usr/local/lib/python3.x/site-packages),
That is my case, too.
but, normally, django projects are deployed somewhere in the web server hierarchy (/var/ww/django in my case, due to old personal tastes), and applications properly defined in the settings.py for the project.
So, the message files are out of reach for manage.py.
Changing to /usr/local/lib/python3.x/site-packages/X (with X being postorius, hyperkitty and django_mailman3) and using django-admin compilemessages all works!
And for me as well. Thanks a lot Victoriano, I owe you a beer
Thanks for pushing my thoughts in the right direction!
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/