Error in `mailman-web conmpress`
Hi,
I'm seeing this in our GSOC student's build of the suite. I don't yet know if it's related to his changes, just wondering if anyone has seen it or has any ideas how to resolve it:
% mailman-web compress --settings settings --pythonpath pwd/var/etc
Compressing... Invalid template postorius/user/address_preferences.html: Invalid filter: 'add_form_select'
Invalid template postorius/user/subscription_preferences.html: Invalid filter: 'add_form_select'
Invalid template postorius/lists/header_matches.html: Invalid filter: 'add_form_select'
done
Compressed 2 block(s) from 106 template(s) for 1 context(s).
add_form_select is not a standard Django template filter, it's
defined and registered in django-mailman3.
On 8/29/23 14:58, Stephen J. Turnbull wrote:
Hi,
I'm seeing this in our GSOC student's build of the suite. I don't yet know if it's related to his changes, just wondering if anyone has seen it or has any ideas how to resolve it:
% mailman-web compress --settings settings --pythonpath
pwd/var/etc Compressing... Invalid template postorius/user/address_preferences.html: Invalid filter: 'add_form_select' Invalid template postorius/user/subscription_preferences.html: Invalid filter: 'add_form_select' Invalid template postorius/lists/header_matches.html: Invalid filter: 'add_form_select' done Compressed 2 block(s) from 106 template(s) for 1 context(s).
add_form_selectis not a standard Django template filter, it's defined and registered in django-mailman3.
Have they installed all the projects from source? I feel it might be causing the issue if they are using the git head of Postorius but not for django-mailman3.
This was added recently in django-mailman3 and hasn't yet been released, so using the released version can cause the above error.
-- thanks, Abhilash Raj (maxking)
Abhilash Raj writes:
Have they installed all the projects from source? I feel it might be causing the issue if they are using the git head of Postorius but not for django-mailman3.
That turned out to be the problem.
This was added recently in django-mailman3 and hasn't yet been released, so using the released version can cause the above error.
I told Durlabh to use either the versions that Mr. Liu used last year or the most recent released versions so he'd have a base we can expect to work and play well together, but he was lazy and went ahead using git HEAD of some of the packages on the argument that it makes syncing to HEAD easier later. :-(
Steve
participants (2)
-
Abhilash Raj -
Stephen J. Turnbull