Update: previously attached patches were incorrectly using subscriber_access in ListGroup, although it's a field of
Listin pgarchives.
Besides, they were not built on top of upstream. Please note that this set of patches is built on top of the patch I
sentin gitlab [1], as upstream currently crashes on migration.
New sets of patched attached.
[1] https://gitlab.com/pglister/pglister/-/merge_requests/33
On 28/02/2023 11:39, Célestin Matte wrote:
> Attached another proposed solution to that problem, with a series of patches for pglister and pgarchives:
> - 0001-Add-subscriber_access-field-to-ListGroup_pglister.patch adds a subscriber_access field in pglister's admin
section
> - 0002-Add-subscriber_access-to-archives-API_pglister.patch adds subscriber_access to the API's archive section in
pglister
> - 0001-pglister_sync-obtain-subscriber_access-from-API_pgarchives.patch uses the value received from the API instead
ofa default "False" that has to be manually changed
>
> As a reminder, the problem was that subscriber_access was set to False by default, which means that any list created
onpglister and set to be archived on pgarchives won't be reachable by subscribers, unless the subscriber_access field
ismanually modified in the database.
--
Célestin Matte