Regarding json vs js format, some considerations

This is now deployed. Can be tested in https://bn.m.wikipedia.org/wiki/%E0%A6%AC%E0%A6%BF%E0%A6%B6%E0%A7%87%E0%A6%B7:Contribute

Confirmed that MT is not available in ja.wiki

I could not reproduce the issue. This is what I get:

I just tried translating a random article to fa. I used Google Translate and then used Yandex. For both of these options, Machine translation is working and I don't get any error message. Screenshot below:

You are seeing Vietanamese because of 'tn' in its English name. This is similar to the situation I explained in https://phabricator.wikimedia.org/T320382#8385627. So use a display language like bn or ml. Sorry for the confusion. The fuzzy matching logic for language search tightly depends on current display language. That makes the experience different for different people.

@Pginer-WMF, eventhough T303522 has decisions on breakpoints, it is initially available only at Codex. This interface we are customizing does not use Codex. So we will have to rely to existing definitions of breakpoints in mediawiki core. But whenever those definitions are updated, Special:Contribute will reflect those changes automatically.

The translate card in Special:Contribute does not make sense in wikis when accessed in mobile and when mobile mode of CX(also known as section translation) is not available. But in T319306: Adjust visibility for the option to translate in the Persistent Contribution entry point we made sure that Translate option card will be shown only when it is a valid option in a mobile/desktop mode in a specific wiki. So that part is covered.

In T320382#8381710, @EChukwukere-WMF wrote:

@santhosh Please correct me if I am wrong, typing tn in the search for the link in question shows Vietnamese here instead of Setswana ?

I did a manual analysis of recently published section translations and could not find any examples. @KartikMistry Can you help to find more examples?

To clarify, this is about the Vue dashboard. Currently we had disabled the selectors for "published", "suggestions", "in progress" by using app.config.globalProperties.$incompleteVersion. Just giving true value will bring all the selectors(they are functional too).

After the fix:

This ticket is a few months old. There is no "In other languages" as of today.

After fix:

fa.wikipedia gets the mediawiki updates in Thursday train. I think you tested it before that.
I tested today and works fine:

Screenshots after the patch:
Desktop- For testing I just duplicated the cards using browser dev tools:

Wide screen	Narrow screen

Hi @Prtksxna , We discussed this in language team.

Test plan:

• Visit: bn.m.wikipedia.org/wiki/Special:Contribute - a wiki where SX enabled in mobile mode. Observe Translate option is present
• Visit: en.m.wikipedia.org/wiki/Special:Contribute - a wiki where SX is not enabled in mobile mode. Observe Translate option is not present
• Visit: en.wikipedia.org/wiki/Special:Contribute - a wiki where CX is enabled in desktop mode. Observe Translate option is present
• Visit: bn.wikipedia.org/wiki/Special:Contribute - a wiki where CX is enabled in desktop mode. Observe Translate option is present
• Visit https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures, disable Content Translation Beta Feature. Then go to Visit: en.wikipedia.org/wiki/Special:Contribute, Click translate option. It should take the user to CX dashboard. Now open https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures again and observe Content Translation beta feature is activated.

• Client-side only: Should generally be avoided, but can be used if a feature is so reliant on JavaScript or modern browser support that a meaningful non-JS alternative isn't feasible. A good example of this is VisualEditor, which is client-side only for that reason. The notifications popup also kind of falls in this category (without JS, the bell icon is just a link to Special:Notifications)

Fixed in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/850122

Just checked. It is not related to this ticket. It is caused by a regression from https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/839427

This came up in code review of https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/849531

I did a quick git bisect and the problem originated from this commit: https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/836254

Test instructions:
Go to https://cxserver.wikimedia.org/v2?doc#/Machine%20translation/post_v2_translate__from___to_:

It seems a regression from https://gerrit.wikimedia.org/r/c/mediawiki/services/cxserver/+/802092. Debugging.

In T318907#8313853, @gerritbot wrote:

Change 842412 had a related patch set uploaded (by Santhosh; author: Santhosh):

[mediawiki/extensions/ContentTranslation@master] SX Eventlogging: Add web_pageview_id and web_session_id to the events

https://gerrit.wikimedia.org/r/842412

Also, mw.config.get( 'wgSectionTranslationMissingLanguages', [] ) is returning the current language. That is not right.

The getMissingFrequentLanguages need a filter for current language, similar to the filtering we did in ULS relevant languages entrypoint

Yes @Jdlrobson.

Yes, we are unblocked on this. Thanks.
Is there a ticket to add "Contribute" item in sidebar menu that takes the user to Special:Contribute?

@Jdlrobson Thanks, this looks great.
I just submitted a patch to add Translations card. Screenshot below:
The ordering of cards looks arbitrary now. Should there be a way to specify the order? For example, what if we want to have 'New page' at top and then 'Translations' after that?

@larissagaulia I have provided the following self assessment. The application is constrained to a special page, a few wikis, only to logged in users. We have deployed the application to a few dozen smaller wikipedias. Because of that we believe the risks are very minimal. But we wanted to get reviewed by performance team. But there is no strict timelines and we are not blocked by it(unless you see anything very wrong here)

In T318495#8266795, @Jdlrobson wrote:

ContentTranslation should be using mw.util.addPortletLink to add this menu item:
https://gerrit.wikimedia.org/g/mediawiki/extensions/ContentTranslation/+/e33dfcb14963a641bfc4c3f92b0dfe716d245517/modules/entrypoints/ext.cx.entrypoints.contributionsmenu.js#112

Filed upstream issue https://github.com/wikimedia/jquery.uls/issues/433
@Pginer-WMF - Could you please comment there on expected behavior for narrow mode?

Technical note after a quick exploration: Implementing custom "no-results-for-search" screen is tricky. jQueyr.ULS accepts an option to pass a function that builds this screen. But that option is already used by mediawiki ULS customization. Overriding that option by another mediawiki extension(CX) is not possible right now. Unless we make MW ULS aware that other MW extensions can customize it - That is too much fragility we are introducing. The behavior will depend which extension registers the "no-results-for-search" first.

@Pginer-WMF, I have a question related to the case "Searching a language that does not exist"

Yes, the page is slow. It is a known issue - Too much data to fetch and render. And becoming slower and slower as more and more historic data accumulates :-)

https://ca.wikipedia.org/wiki/Especial:ContentTranslationStats is loading the stats and graphs now.

After the fix:

@Pginer-WMF It is unclear on what is remaining on this ticket. Since this is not an active area we are working these days, I suggest we either close or park it out of current sprint.

A fix has been deployed and since this ticket is about a one off issue, we will have to follow the process in T307967 by closing it and monitor if issue happens again.

In T290436#8216494, @EChukwukere-WMF wrote:

using the article https://en.wikipedia.org/wiki/Ndowa_Lale as stated the "Edit Language Links" is not available

This is a regression from https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/820893