Postorius web issues after upgrading mailman 3
Hello,
I hope someone could help me in relation to this issue. I have experienced some error with my mailman3 deployment (only in postorius web) after went through the upgrading procedure following https://docs.mailman3.org/en/latest/upgrade-3.2.html#upgrading-mailman-3 I believe this is nothing else then the wrong css/js files gone to the wrong directory or they aren't implemented properly. Basically some part of it works ok and some doesn't. The following web pages doesn't seem to be implementing the css/js files is Archives, Account, Posting Activity, Log in and Log out web pages. Any help would be appreciated.
Regards, Tibor
On 10/12/21 8:38 AM, Tibor Molnar wrote:
Hello,
I hope someone could help me in relation to this issue. I have experienced some error with my mailman3 deployment (only in postorius web) after went through the upgrading procedure following https://docs.mailman3.org/en/latest/upgrade-3.2.html#upgrading-mailman-3 I believe this is nothing else then the wrong css/js files gone to the wrong directory or they aren't implemented properly. Basically some part of it works ok and some doesn't. The following web pages doesn't seem to be implementing the css/js files is Archives, Account, Posting Activity, Log in and Log out web pages. Any help would be appreciated.
These are all HyperKitty pages, not Postorius.
Did you run all the post-upgrade tasks mentioned at <https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade> after upgrading?
Also, it is possible, but not the likely cause of this, that there is an incompatibility between the latest hyperkitty and django-mailman3 in PyPI. See <https://gitlab.com/mailman/django-mailman3/-/issues/48>. You could try
pip install -U git+https://gitlab.com/mailman/hyperkitty.git
and see if that helps.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Tibor,
I have the same (or a very similar) issue. Have you tried getting jquery-1.11.3.min.js from somewhere on the Internet and move it to
<your path here>/static/postorius/libs/jquery/
That fixed it for me.
For the docker versions, there is an open issue on this: https://github.com/maxking/docker-mailman/issues/519
Kind regards
- M4tze
Am 12.10.21 um 17:38 schrieb Tibor Molnar:
Hello,
I hope someone could help me in relation to this issue. I have experienced some error with my mailman3 deployment (only in postorius web) after went through the upgrading procedure following https://docs.mailman3.org/en/latest/upgrade-3.2.html#upgrading-mailman-3 I believe this is nothing else then the wrong css/js files gone to the wrong directory or they aren't implemented properly. Basically some part of it works ok and some doesn't. The following web pages doesn't seem to be implementing the css/js files is Archives, Account, Posting Activity, Log in and Log out web pages. Any help would be appreciated.
Regards, Tibor
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/
Hi Mark,
Thanks for pointing out that this is a hyperkitty web error. I did run all the post-upgrades without errors. I have also tried upgrading hyperkitty with the command you are suggested but nothing has changed after.
Hi M4tze,
The postorius web page is working ok for me, I'm only having issues with the hyperkitty pages. I have lookaed at the file you suggested me to download but I already have that in the correct place.
On 10/13/21 8:23 AM, Tibor Molnar wrote:
The postorius web page is working ok for me, I'm only having issues with the hyperkitty pages. I have lookaed at the file you suggested me to download but I already have that in the correct place.
What does the alias for /static/ in your web server point to?
What does
diff -r dir1 dir2
show where dir1 is the hyperkitty subdirectory in the above directory and dir2 is the hyperkitty/static/hyperkitty in your Mailman installation.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Ok the alias on webserver is pointing to: Alias /mailman3/static /var/lib/mailman3/web/static
no difference between the two directories of hyperkitty
/var/lib/mailman3/web/static/hyperkitty
/usr/local/lib/python3.8/dist-packages/hyperkitty/static/hyperkitty
On 10/19/21 2:33 AM, Tibor Molnar wrote:
/var/lib/mailman3/web/static/hyperkitty
/usr/local/lib/python3.8/dist-packages/hyperkitty/static/hyperkitty
If you examine the source of your HyperKitty pages that have the issue,
what do you see for the hrefs in the <link rel="stylesheet" tags in
the <head> section.
Also, I don't know if it is significant or not, but https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade says to run
(venv) $ mailman-web compress
(venv) $ mailman-web collectstatic
I always run those in the other order. I suggest you do
mailman-web collectstatic --clear mailman-web compress
(or whatever your django admin command is) in that order and see if that helps.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
M4tze -
Mark Sapiro -
Tibor Molnar