We fetch curated content for 'Onwards' containers using a hard-coded list of collection ids. This includes au-alpha/news/regular-stories. But there is no collection with that id in the current PROD fronts config, so no data is fetched for Australian news articles.
UK edition has two containers, as it should
https://www.theguardian.com/australia-news/2022/aug/31/federal-icac-independents-want-safeguards-to-ensure-body-cannot-be-politicised
AU edition only has one container, when it should have two
This collection id does exist in the CODE fronts config, so my guess is that it has been removed from PROD at some point (rather than it being a typo or something). If this is correct, we probably need an editorial decision about which collection to use instead for AU/News curated content.
nb. This is a bug both in the existing site and in the new curated content agent that's being created at the moment. If we get a new id, it should just be a one-line change in either codebase, however.
If we're going to talk to editorial about this, it may also be worth exploring whether there are any options which would allow us to avoid relying on a hard-coded list of ids altogether.
We fetch curated content for 'Onwards' containers using a hard-coded list of collection ids. This includes
au-alpha/news/regular-stories. But there is no collection with that id in the current PROD fronts config, so no data is fetched for Australian news articles.UK edition has two containers, as it should
https://www.theguardian.com/australia-news/2022/aug/31/federal-icac-independents-want-safeguards-to-ensure-body-cannot-be-politicised
AU edition only has one container, when it should have two
This collection id does exist in the CODE fronts config, so my guess is that it has been removed from PROD at some point (rather than it being a typo or something). If this is correct, we probably need an editorial decision about which collection to use instead for AU/News curated content.
nb. This is a bug both in the existing site and in the new curated content agent that's being created at the moment. If we get a new id, it should just be a one-line change in either codebase, however.
If we're going to talk to editorial about this, it may also be worth exploring whether there are any options which would allow us to avoid relying on a hard-coded list of ids altogether.