Setting archive_policy "private" using REST changes web UI setting Archive policy, but does not hide archive until UI Save
I am working on disabling a list removing all members using REST and then setting archive_policy to "private" also using REST. This changes the UI Archive policy setting to Private archives as I would expect, but I just discovered that the (now previous) member, still logged in, and alså public (not logged in), still have access to the archive. It is not browser cache.
At the moment I click Save in the UI settings/archiving, both logged in user and not logged in user (other browser) changed to "This mailing list is private. You must be subscribed to view the archives." on page reload.
It seems that i need to click Save on every list having been changed, before the archive is hidden. Is that a bug?
I am currently using Postorius Version 1.3.5 and HyperKitty version 1.3.4.
/Henrik
On 8/14/24 01:15, Henrik Rasmussen wrote:
I am working on disabling a list removing all members using REST and then setting archive_policy to "private" also using REST. This changes the UI Archive policy setting to Private archives as I would expect, but I just discovered that the (now previous) member, still logged in, and alså public (not logged in), still have access to the archive. It is not browser cache.
At the moment I click Save in the UI settings/archiving, both logged in user and not logged in user (other browser) changed to "This mailing list is private. You must be subscribed to view the archives." on page reload.
It seems that i need to click Save on every list having been changed, before the archive is hidden. Is that a bug?
The daily Django hyperkitty sync_mailman job will probably do it.
Or, you can figure out what REST calls saving the settings in Postorius does and do that.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Henrik Rasmussen -
Mark Sapiro