Page MenuHomePhabricator

Check current support for temporary accounts in Section Translation on mobile
Closed, ResolvedPublic

Description

Temporary accounts are a new type of account that gets automatically created when logged-out users contribute to a wiki.

Section Translation on mobile was designed to work as much as possible without requiring a user account but there may be assumptions depending on a logged-in user. Ideally, users with a temporary account should be able to use the tool to start (by searching or using suggestions), continue and publish (in any namespace) translations without issues.

This ticket is intended to test whether that is the case and capture issues found when trying to use the tool with a temporary account. The focus is on Section Translation on mobile.

Additional considerations:

  • Entry points assume that anonymous editor will not access the tool
  • Temporary accounts expire by no longer provide access to the user, which may result in drafts remaining unpublished for a long time (until automatically deleted).

A similar task exists for the desktop experience: T345254: Check current support for temporary accounts in Content Translation on desktop

Result: After the investigation, the follow-up adjustments are captured in T353239: Support creation of temporary users when anonymous ones reach the mobile/desktop editors in Content Translation

Event Timeline

Section Translation UI and its core API endpoints ("sxsave" for auto-saving, and "cxpublishsection" for publishing) can properly handle temp users the same way, they are treating named users. As far as our application is concerned, there is no difference between temp and named users, since temp users have a global user id which is what we require from a user.

On the other hand, this is not the case for anonymous users, as we would need to make some adjustments if we want to support them.

Adding to my previous comment, we can easily support anon. users, by creating a temporary user and starting a new session for this temp user, during auto-save requests. Then, the user will be treated as temp user, which is equivalent to named user as far as SX is concerned.

@Pginer-WMF since the investigation for this task has been completed (same for desktop devices: T345254), do you think we can consider these tasks completed and maybe work on T353239 as a next step?

Pginer-WMF claimed this task.

@Pginer-WMF since the investigation for this task has been completed (same for desktop devices: T345254), do you think we can consider these tasks completed and maybe work on T353239 as a next step?

Makes sense. Thanks for the investigation @ngkountas!