Jump to content

Fix persistent markup leakage from Content Translation tool (Community Wishlist/W550)

Prioritized
From Meta, a Wikimedia project coordination wiki

View all wishes.

Description

The Content Translation tool (CX2) frequently injects malformed wikitext into published articles, leading to errors in reference lists (example).

Namely: in repeated references, the tool is leaking <span class="cx-segment"> tags (example), and corrupted citation structures, such as <ref name="...">...<cite class="citation web cs1" data-ve-ignore="true">...</cite></ref>; (example), resulting in error messages like Cite error: Invalid <ref> tag; name "Author2026" defined multiple times with different content.

This is a longstanding issue that persists despite years of reporting (T144167 and T287936). These errors require significant manual intervention from experienced editors to fix after publication:

  • An older global filter has caught more than 6000 cases of the former issue: Global Filter 192 (~1 page/day)
  • A new filter has been set up to track the latter issue: Global Filter 401 (~170 pages/day; disabled after acquiring enough samples, over around 4½ days)

Content Translation is intended to lower the barrier to entry for editors, but it is currently confusing inexperienced editors and creating a cleanup debt that falls on the shoulders of the community.

Assigned focus area

Unassigned

Type of wish
Bug report
Tags
Affected users

editors, patrollers

Phabricator tasks
Other details
  • Created: 22:52, 8 June 2026
  • Last updated: 09:33, 18 August 2026
  • Author: Ponor (talk)
Voting

This wish currently has 25 supporters. Voting for this wish is open until it is completed.

Supporters of this wish
Support Ponor (talk) 22:52, 8 June 2026
Support Pppery (talk) 00:29, 9 June 2026
Support Runolist (talk) 07:09, 9 June 2026
Support Developing software is great, but keeping it up and running over the years is even more important—especially when volunteers are asked to handle these time-consuming tasks for ages! Framawiki (talk) 13:43, 9 June 2026
Support In 2024 I had to write a custom Pywikibot script just to address this issue on my home wiki, but it's far from perfect. Would be much more optimal to cut out the middle man and address the issue at hand MonAx (talk) 13:46, 9 June 2026
Support It takes a lot of time to fix those problems. RajatonRakkaus (talk) 13:54, 9 June 2026
Support MMH (talk) 16:16, 9 June 2026
Support Фіксер (talk) 17:48, 9 June 2026
Support ZebaX (talk) 19:31, 9 June 2026
Support My 5839 changes (due to this issue) in Spanish Wikipedia will support the idea :) Superzerocool (talk) 21:26, 9 June 2026
Support Nemoralis (talk) 02:40, 10 June 2026
Support Every time I publish the Content Translation I need to run through https://mdwiki.toolforge.org/fixwikirefs.php or similar tools to clean up the reference, to the point of troublesome. Hopefully the related issues could be solved in the near future. Hakimi97 (talk) 04:07, 10 June 2026
Support Escargot bleu (talk) 07:10, 10 June 2026
Support Repakr (talk) 07:36, 10 June 2026
Support Likskyl (talk) 07:25, 11 June 2026
Support Fuyo21 (talk) 20:25, 12 June 2026
Support Having to manually clean up the references when translating is very annoying. Asilvering (talk) 23:09, 12 June 2026
Support Hm, this issue needs urgent repair ASAP. نوفاك اتشمان (talk) 15:13, 13 June 2026
Support Yes has been a persistent problem. We have partly fixed it at Wiki Project Med in our version of the tool by expanding the references followed by shortening them after publication. Doc James (talk) 09:14, 15 June 2026
Support CX needs to be made as less clunky as possible given that it is one of the most used tools for new users to create articles. Klein Muçi (talk) 09:46, 18 June 2026
Support Strainu (talk) 13:15, 18 June 2026
Support Red Sneak (talk) 11:04, 22 June 2026
Support Let's fix this because bad publicity is resulting from bad content attributable to this bug. RememberOrwell (talk) 18:33, 3 July 2026
Support Warudo (talk) 22:40, 17 July 2026
Support Addonian1123 (talk) 09:04, 4 August 2026