Translations in Content Translation (CX) involve two languages. When creating a new translation, CX redirects the user to the target Wikipedia so that articles are created locally.
This means that a user in the Spanish Wikipedia CX dashboard can start a translation from Spanish to Catalan, andand, as a result he will be redirected to Catalan Wikipedia's CX translate editor.lt, This redirect allows CX to present an integrated view of all translations (the user does not have to figure out to which site to start a translation from),he will be redirected to Catalan Wikipedia's CX translate editor. but avoidThis redirect allows CX to present an integrated view of all translations (the user does not have to figure out which site they should start a translation from) while avoiding cross-wiki saving issues.
When CX is isolated as a beta feature, the redirect may be problematic since the user needs to have the beta feature enabled for each of the languages involved. If that is not the case, the user will get a page not found error instead which will break the user experience badly.
To avoid this issue, we can allow access CX even if the beta feature is disabled only in the case of being part of the described redirection. The rationale is that the user has already enabled the beta feature on a site, and is clearly expressing the intent to start a new translation for which reaching CX will provide less surprise than getting an error message.
**Acceptance criteria:**
* When coming using a link from a wiki where CX is enabled, the SpecialPage will work as if the beta feature is enabled in the target wiki.
* The beta feature will not become actually enabled in the preferences in the target wiki and will not be otherwise available unless explicitly enabled.