@SBisson in testwiki I cannot 'Mark for deletion' with 'Redirect for discussion' option. The action never finishes and the Console displays the error (it could work differently in enwiki, of course):

After playing with prototype, here are my few suggestions

Checked in betalabs and testwiki.

Added to the list of tasks to be monitored after deployment.

Checked the fix after deployment - PageTriage nominating for deletion options and Twinkle options (specifically PROD). The pages's state is consistent with ptrp_deleted tag.

Checked the fix - the grey links will be published as text, for example - grey links from translation panel:

The issue is not present in wmf.24 with cx2. The issue is still present in cx2-testing where the issue was originally reported.

@KartikMistry - has cxserver been deployed? The issue is still present in testwiki (wmf.24) although Apertium handles the translation as per @Petar.petkovic comment's screenshot. The translation of quote template still silently fails in cx2 (both for Apertium and Yandex(of course)).

There are still Yandex-related errors (and 'Automation translation failed' warning is displayed') for attempting to translate the infobox and a paragraphs with {{Curiosity Mission Timer}}:

Checked in betalabs - the pages were nominated for deletion with [[Category:All_articles_proposed_for_deletion]] (thx, @SBisson).
ptrp_deleted gets updated when the category is removed and 'Nominated for deletion' filter won't fetch it.

The patch seems to be deployed to wmf.24 but the issue is still there. The article en: Curiosity (rover) has 37 Template:'s and there are two paragraphs that have the template but one can be translated and another is not and 'Machine translation failed' message persistently appears.

Thanks, @SBisson's suggestion works - all seem to be in place. flowdb is present with all tables.

Resolved with the patch in T205616: CX2: Section alignment broken when translating "Fleming: The Man Who Would Be Bond" from Hebrew:
for en:Triops longicaudatus
from

@Petar.petkovic yes, the patch fixed T205679: [wmf.23] CX2: Unable to translate "Triops longicaudatus" - TypeError: model.getSectionNumber is not a function too. The source panel does not look ideal, but the major display bug is gone.
I did some more testing to make sure that there are no specific LTR issues with translation and all look fine. I closed T205679: [wmf.23] CX2: Unable to translate "Triops longicaudatus" - TypeError: model.getSectionNumber is not a function too.

Checked in cx2 and enwiki (wmf.24) - errors and warnings are preservedl when a translation with issues is loaded, the warnings are in place.

Re-checked the links - the diffs have 'danken' links, so from diff 'thank' action could be done:

Re-checked with cx2 version - the publishing functionality for Reflist is limited in cx2-testing, but all generated markup for references is displayed correctly when all templates are available (for example in betalabs).

Checked enwiki (wmf.24) - ORES filters work as expected.

Thanks, @SBisson - all makes sense.

@kostajh I've enabled mediawikiflow and flow roles. Logged in to local env and enable Flow on a user talk page. The flow tables were created in enwiki db. The user talk page displays the following error:

@Trizek-WMF please take a look if everything is in place - the screenshot below is from betalabs and the message displayed is from https://translatewiki.net/w/i.php?title=Special:Translations&message=MediaWiki%3AWikimedia-copyright (the specific reference was mentioned in your comment).

I checked in enwiki (wmf.23 with ?ores=true). @SBisson - thank you for the queries, they are really helpful.

The log is present and all log functionality checked (filtering options, deletion/suppression of log entires) - @MMiller_WMF please take a quick look- https://en.wikipedia.beta.wmflabs.org/wiki/Special:Log?type=pagetriage-copyvio&user=Etonkovidova&page=&wpdate=&tagfilter=:

Checked in betalabs. @kostajh I think the position of labels on small screens (including mobile) looks quite decent.

@Nikerabbit - Since I am not 100% sure that this fix has addressed what it's supposed to fix, please review my comment below. It could be that what I've observed is unrelated to the scope of this fix.

I re-checked the following section types in testwiki (wmf.24) with cx2 enabled:

• • Article title
  • Sections title
• Infoboxes
  • Images with MT translated description
  • tables

The MT translation of the above does not trigger MT abuse message. The calculation (the progress bar) will, indeed, indicate that there is 100% Machine translation (e.g. translated only images in en:Triode, the calculation bar will say 12% translated and 100% machine translated).
It's a relatively small usability issue - users may be confused why sometime 100% MT translation displays the warning and sometime is not. It might be a good idea to exclude MT translated specific section type from that progress bar calculation.

Checked in betalabs and testwiki(wmf.24)

Checked in wmf.23 - references displayed correctly and no Console errors are displayed.

@zeljkofilipin Let's keep this task around until more specific tasks will be added.

I re-checked in enwiki (wmf.23) - en:Orthogonal frequency-division multiplexing to Spanish warnings will display <br>:

@Pginer-WMF - please review the following results of comparative reference testing
(1) The issues related to references and the Console errors associated with them have been reported across several tickets:

@He7d3r
I re-checked the first reported case - the example of the formula that needed to be inserted manually, e.g. \vec{f} e \vec{g} (https://pt.wikipedia.org/wiki/Fun%C3%A7%C3%B5es_ortogonais?diff=45888620).

I re-checked with cx2-testing - yes, the issue is present, but to get the same screenshot as in the ticket, I need to get to about 701px or less not to 900pxwide as was mentioned.

Checked in wmf.23 - the element <li id="pt-uls" class="active"><a href="#" class="uls-trigger">English</a></li> seems to be identical on both pages: Special:ContentTranslationStats and Special:ContentTranslation

Re-checked in wmf.23 with cx2 - the template displayed correctly in the source article panel. However, cx2 display of such templates is still problematic.

Checked in betalabs - the filters' logic seems to be accurate. I am having general problems with Page Curation tool - i.e. cannot submit any page in User namespace for Page triage, and cannot mark a page for deletion. I'll need to sort such issues out with @SBisson on Mon whether is just betalabs limitations or something else.

Checked the fix in betalabs - all is fine.

Checked in betalabs - generally, the sort option is preserved between state filters, e.g. if a user switches from 'Declined' +'Declined date (oldest)' to 'Awaiting review', the sorting order for 'Awaiting review' will automatically become 'Submitted date (oldest)'.

Checked the fix in enwiki (wmf.23) - switching between translation version is fine. Also &version=1 or &version=2 will be correctly displayed in the url.

@SBisson

[...] the task description pretends there was one such banner on IE11.

@santhosh

[...] we need to identify some section types where we don't need to do abuse checking. Examples are infoboxes, tables, reference list, headings.

I checked the patch which states that the following should be excluded:

'cxBlockImage', 'mwBlockImage', // Both are required since new images can be inserted too.
'cxTransclusionBlock', 'mwTransclusionBlock',
'mwTable', 'list', 'mwHeading'

Checked in betalabs and testwiki (wmf.23). Betalabs has quite few pages that were not scored by the new articlequality, e.g. oresc_rev=385173.

Just a suggestion for simplifying things - keep the behavior (sort order changes to 'Created day (newest)' ) but only when a user clicks on 'Set filters' button not on 'Set filters' link.

Interesting - I tried to test it with test user who did not have ContentTranslation beta feature enabled - it was possible to Disable cx2 but only once. After that I tried o switch to a different browser, clear all browser history, reset all user settings to default - I cannot disable cx2.

Checked in testwiki (wmf.23) - the issue is fixed.

@Petar.petkovic I was testing in testwiki. I think that I missed one step in the description - to actually translate some text, not simply opening articles with different versions. After that the version 2 selection gets stuck.

@santhosh - the problem is present in production now - testwiki (wmf.23). Only Basic references can be edited - clicking on the reference and then on 'Edit' does not open the editing box.