-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newsroom pages aren't updated with the latest news #2480
Comments
Will do a quick fix |
Fixed this for all news that went missing. Will see if there are any issues with the new ones , if not we are good to close. I have updated the webhook which I missed to update after i18n. |
28 th Aug news publish did not trigger webhook, so the news is not indexed. So manually trigger the indexer function. |
11th sep news is not indexed. Modified the webhook to trigger on create not on update. |
Confirmed that the news is indexed on 17 th sep |
@padms - any test criteria for this one? I can also confirm that new news are showing on the /news page. |
@meols No specific criteria to test as this is happened in prod. Two things were done to fix
I observed the newsroom for the last two news articles published and they were indexed immediately. |
Thanks @padms - I agree, this can be closed. |
We see that neither the no or the en newsroom is updated with the latest news.
I published a news today that is visible on the homepages, but not on the newsroom pages. The English newsroom is just missing the latest news (from today), but the Norwegian newsroom is missing the one from today and two more.
![image.png](https://camo.githubusercontent.com/5d5f4327806d19fc95980c4879612a9d4e7643cc171b20fc94041efae2838c42/68747470733a2f2f6170692e7a656e6875622e636f6d2f617474616368656446696c65732f65794a66636d467062484d694f6e73696257567a6332466e5a534936496b4a42614842424b326c42516d633950534973496d563463434936626e56736243776963485679496a6f69596d7876596c39705a434a3966513d3d2d2d343562656239376266313539393564363831313630316635323466363832623734663363613735382f696d6167652e706e67)
The text was updated successfully, but these errors were encountered: