1148820 - The JSON version of a page is missing the summary content for its translation

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: API, enhancement)

Description

[Jeremie Patonnier :Jeremie]

What did you do?
================
Request that page in English:
https://developer.mozilla.org/en-US/docs/Glossary/AJAX$json

And the same page translated in French
https://developer.mozilla.org/fr/docs/Glossaire/AJAX$json

What happened?
==============
When you look at the 
{
  translations: [
    {
      summary: ""
    }
  ]
}

The translation summary is provide with an empty string.

What should have happened?
==========================
The translation summary should be filled with the SEO summary extracted from the translated page.

Is there anything else we should know?
======================================
This make that the {{Glossary}} macro has to do 3 request instead of two to work. This lead to unnecessary overload on KumaScript.

Comment 1

[Florian Scholz (Open Web Docs)]

PR submitted: https://github.com/mozilla/kuma/pull/3175

Comment 2

[MDN Team (:mdn-dev)]

Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/79e2ee2503f67e6b7befd3c1f48d12b8f6aff7c6
Fix bug 1148820: Properly get the summary for translations in jsons

https://github.com/mozilla/kuma/commit/d79d0c21af5488be806e933f5d6de66222f3b372
Merge pull request #3175 from Elchi3/bug1148820

Fix bug 1148820: Properly get the summary for translations in jsons

Comment 3

[Luke Crouch [:groovecoder]]

This is pushed to production, but since the summary is put into the JSON during a page save, I'm afraid the pages have to be saved again to re-populate the value? :/

Comment 4

[Florian Scholz (Open Web Docs)]

Force-refreshing pages also works. Thanks for merging and pushing :)

(Ideally we would re-render all our documents to get this populated everywhere. We requested this several times already, but it happened only with Les' script ages ago, see also bug 1094452 for current ideas/approaches)

Comment 5

[Jeremie Patonnier :Jeremie]

While investigating that bug with Jannis, he was worried by the fact that the summary doesn't seams to be properly cached in DB. So this bug fix could lead to some performance issue. Maybe a follow up of this bug is necessary to check that out. I needinfo Jannis for his opinion on this.

Comment 6

[Florian Scholz (Open Web Docs)]

Might be related/dealt with in bug 1082616.