Thank you for your quick reply! Comments below.
On Sun, Aug 11, 2019 at 10:03 PM Abhilash Raj <maxking@asynchronous.in> wrote:
I would recommend that you bump up to 3.7 for the web part too, mostly because 3.5 is now has been in security maintenance state for a while. We will drop support for 3.5 after this next release (so you do have some time :), but I fear there *could* potentially be other dependent libraries who might have dropped 3.5 support.
Even though we do run CI and we'd (hopefully) know when there is a dependent library seriously breaking, but since we don't pin down versions, newer releases can cause problems.
The web-server plugin I assume is mod_wsgi?
Good information. Of course it is mod_wsgi.
If you use a separate wsgi server than the one embedded in web-server, you can bump versions a bit more easily. gunicorn or uwsgi are recommended options. Do note that the new version of Mailman Core also uses gunicorn now.
That might be simpler although I probably still will have to use apache as passthrough as there are other things on that server using port 443 (80) and yet another server running is not what I'd like even if wsgi is a server process anyway as I understand it. I'll consider that and change it.
- The index page with all lists is not sorted in any useful way
although it is based on something as the order seems to be stable. Prior to the upgrade the lists were sorted in alphabetical order after list name which is a lot more usable for me as admin. If I click the link at the bottom with "click to view all lists" I get the old behaviour.
This change was made so that you will see only the lists you are a member of either as a subscriber, moderator or owner. This is default when you are logged-in, but when logged-out, you will see the old view with all lists alphabetically sorted.
That is very good. It still is strange that this view is not sorted.
Are you sure the migrations are there? I can see the following list on the latest git master of Postorius (all the ones after 0004_ are related to emailtemplate):
I thought so, but it seems as if they are not. That said I have not used django for anything else. After setting up the django-admin-script and modifying a few paths I got it to work correctly. The run I had made did not work although it also failed silently. Had I been used to django I'd known that it should print "OK" and ticked boxes for performed migrations, but I just use django for mailman-things.
So now it works. Great.
Thanks! // David