Page MenuHomePhabricator

Enable Content Translation beta feature for a user when accessing a Section Translation entry point on mobile
Closed, ResolvedPublic2 Estimated Story Points

Description

On wikis where Content Translation is not available by default yet, Section Translation is only visible to those users that have the Content Translation beta feature enabled. Since beta feature setting are hard to access on mobile, we may want to provide an easier way to access Section Translation.

This ticket proposes to automatically enable the Content Translation beta feature when users access Section Translation entry points (T286641) on mobile. For example, a user looking for an article in their language may get an option to translate it (T286645), by accepting such invite the user would access Section Translation, enabling the beta feature automatically if needed.

This allows to enable Section Translation for more wikis that may not be ready for getting Content Translation by default, and the creation of entry points that require the tool to be available in all languages (T286470).

Event Timeline

Pginer-WMF triaged this task as Medium priority.Dec 20 2021, 1:43 PM
Pginer-WMF created this task.
Pginer-WMF moved this task from Backlog to Entry points on the SectionTranslation board.
santhosh set the point value for this task to 2.Apr 5 2022, 5:56 AM

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

[mediawiki/extensions/ContentTranslation@master] SX: Enable CX beta feature when landed on Special:CX with valid campaigns

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

santhosh added subscribers: KartikMistry, santhosh.

@KartikMistry please add the following campaigns as valid campaigns to CX ContentTranslationCampaigns configuration in production

"mflanguagesearcher" => true,
"mfrecenttranslation" => true,
"mfrecentedit" => true,
"mffrequentlanguages" => true,

There is a small issue now - SX campaign names are valid for CX too. Is that a problem? For example, A user in desktop can get CX betafeature enabled if mflanguagesearcher is used in URL. Eventhough technically, it is a campaign related to SX.

Change 777343 merged by jenkins-bot:

[mediawiki/extensions/ContentTranslation@master] SX: Enable CX beta feature when landed on Special:CX with valid campaigns

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

There is a small issue now - SX campaign names are valid for CX too. Is that a problem? For example, A user in desktop can get CX betafeature enabled if mflanguagesearcher is used in URL. Eventhough technically, it is a campaign related to SX.

Thanks for flagging this. I think that is not a problem. Eventually Content and Section Translation will become more unified and the different entry points will have both mobile and desktop versions.
Right now it is a bit limiting that it is not possible to expand articles on desktop and the mobile experience is not available in all languages, but having these campaigns register should not be much of an issue.

Change 778381 had a related patch set uploaded (by KartikMistry; author: KartikMistry):

[operations/mediawiki-config@master] Add SectionTranslation entry points as campaigns

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

Change 778381 had a related patch set uploaded (by KartikMistry; author: KartikMistry):

[operations/mediawiki-config@master] Add SectionTranslation entry points as campaigns

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

To avoid any breakage, I'll plan to schedule deployment of this once wmf.7 is in at least Group 0 on Tuesday, April 12th.

Change 778381 merged by jenkins-bot:

[operations/mediawiki-config@master] Add SectionTranslation entry points as campaigns

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

Mentioned in SAL (#wikimedia-operations) [2022-04-13T07:08:03Z] <kartik@deploy1002> Synchronized wmf-config/InitialiseSettings.php: Config: [[gerrit:778381|Add SectionTranslation entry points as campaigns (T298029)]] (duration: 01m 03s)

@EChukwukere-WMF See T286645's description on testing entry points for SX. It can be directly tested in Production where Section Translation is already enabled. @Pginer-WMF can help if any other clarification in the workflow is needed.

Thanks @KartikMistry Tested using description from T286645.

See attachment