400 Bad Request when administrator tries to selectively override member options
This is probably Design Intent, but I'd just like to confirm.
When an administrator submits partial 'member options', it comes back with the details of a 400 - Bad Request, indicating essentially that all of the member options must be set.
Screenshot: https://ibb.co/pzM5Z4m
It would be a bit smoother to check that all values are selected before sending the request, and inform the administrator that they cannot selectively override member settings for their list.
But most importantly, I would like to confirm that nothing is corrupt/broken in our implementation.
Thanks in advance for any guidance.
On 5/8/21 1:17 PM, ieso@johnwillson.com wrote:
This is probably Design Intent, but I'd just like to confirm.
When an administrator submits partial 'member options', it comes back with the details of a 400 - Bad Request, indicating essentially that all of the member options must be set.
Screenshot: https://ibb.co/pzM5Z4m
It would be a bit smoother to check that all values are selected before sending the request, and inform the administrator that they cannot selectively override member settings for their list.
But most importantly, I would like to confirm that nothing is corrupt/broken in our implementation.
What Postorius version is this?
I just tried it on Postorius 1.3.5b1 (The HEAD of the gitlab branch),
and for a user with no options at all set at the list level, I was able
to set Receive own postings only with no problem.
I think this is https://gitlab.com/mailman/postorius/-/issues/178 fixed in Postorius 1.2.0 by https://gitlab.com/mailman/postorius/-/merge_requests/321
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
ieso＠johnwillson.com -
Mark Sapiro