Recent changes for caching policy/doc status pages' management?

MDN
1

Hello there,

Was there a recent modification regarding the way doc status pages (esp. l10n doc status pages) behave?
As far as I can tell, since the end of last week (3-4th Jan 2019), when I refresh/hard refresh this kind of page, I don’t get “fresh” content in the table and some “out of date” pages are actually up to date (at least regarding the last edit date).

I’ve waited a few days but I have the impression I still get some “out of date” pages from last week.
Has anything notable changed regarding this matter?
Thanks for the feedback :slight_smile:

P.S. Looking forward for localizing/documenting in 2019 :fireworks:

2

I’m not aware of any recent change. Can you give an example of an out of date entry from the JS status page?

3

Thanks @jwhitlock.
The l10n doc status for JavaScript in fr lists extends as out of date when the last edit in fr is from the 4th Jan. 2019 and the last edit in en-US is from the 13th Dec. 2018.

The page for Function.prototype.bind is another example of such a case.

4

You probably have to force refresh the doc status page to refresh the {{DocStatus}} macro.

5

The issue is that the document JSON shows the last French edit on 2018-11-18, and the English page on 2018-12-13. There are issues with the JSON being stale for translation data, since it is only updated when the English document is updated, see bug 1320843.

1 Like
6

Thanks @jwhitlock :slight_smile: I had this kind of issue on a few pages in the past but it disappeared after a while. I wasn’t sure it was the same bug in this case (CDN, etc.) so thank you very much for the analysis.
@exe-boss thanks too (though I hard refresh this kind of pages quite often ^- ^)

1 Like