Looking at the acceptance criteria on the parent task, we need to confirm the current behaviour when trying to access a page cross-wiki.
Test each given scenario and report:
A) what happens
B) if redirection is definitely required.
Timebox: 1 day
Looking at the acceptance criteria on the parent task, we need to confirm the current behaviour when trying to access a page cross-wiki.
Test each given scenario and report:
A) what happens
B) if redirection is definitely required.
Timebox: 1 day
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | ifried | T323228 [EPIC] Support global implementation for CampaignEvents extension | |||
Invalid | None | T341788 Redirect the user to the wiki where the event registration was created | |||
Resolved | cmelo | T344441 [SPIKE] Investigate what behaviour is currently exhibited on these special pages |
Here are the special pages we have on our extension and the reason in my opnion why it shoud be redirected or not:
special page | Needs redirect? | why? |
Special:CancelEventRegistration | No | The action in this page requires the event ID and the user ID to cancel the user registration, since we store the central user ID we can allow the user to cancel the registration from any wiki |
Special:DeleteEventRegistration | Yes | We need to check not only if the user is the organizer of this event, but also if this user is still in the "Organizer user group", users can be removed from a user group, which in this case means that this user is not allowed to do any organizer action anymore, although this is an edge case, in case we are fine with this or if we implement a way to check if a user has the user right on the wiki of the event page we do not need the redirect here, if not we need it. |
Special:EditEventRegistration | Yes | On the edit form organizer can change the event page (which needs to be on the same wiki), and can also add other organizers and since users groups are local it needs to be done on the wiki where the event registration was enabled |
Special:EventDetails (as organizer) | Yes | Event organizers can use the "message tab" to send emails to participants, the selected participants may not have An email associate with their account or even an account on a different wiki rather than the one this user register for the event (although we can use the global user ID to get the email address, if we could do that I think we do not need the redirect here) |
Special:EventDetails (as participant or not logged user) | No | Just a note: "View event page" button must always redirect the user to the event page |
Special:RegisterForEvent | No | The action in this page requires the event ID and the user ID to register/update the user registration, since we store the central user ID we can allow the user to register from any wiki. |
Special:MyEvents | No | The user can list the list of event she/he created since we use the global user ID to get the list we don't need to redirect |
Special:MyEvents (Kebab menu "Edit") | yes | The "Edit" action on the kebab menu on this page should always redirect the organizer to the wiki where the event registration was created |
Special:MyEvents (Kebab menu "View event page") | yes | This not like a "real redirect" the event page must always open on its wiki |
Special:MyEvents (Kebab menu "Close registration") | Yes | We need to check not only if the user is the organizer of this event, but also if this user is still in the "Organizer user group", users can be removed from a user group, which in this case means that this user is not allowed to do any organizer action anymore, although this is an edge case, in case we are fine with this or if we implement a way to check if a user has the user right on the wiki of the event page we do not need the redirect here, if not we need it. |
Special:MyEvents (Kebab menu "Delete Registration") | Yes | We need to check not only if the user is the organizer of this event, but also if this user is still in the "Organizer user group", users can be removed from a user group, which in this case means that this user is not allowed to do any organizer action anymore, although this is an edge case, in case we are fine with this or if we implement a way to check if a user has the user right on the wiki of the event page we do not need the redirect here, if not we need it. |
Also:
Mostly looks good, although I think the best strategy might vary by page and "redirect" is not necessarily the best. A few notes:
More generally, it seems to me that the main reasons why we'd need to redirect are 1) checking organizer right, 2) entering the event page (in the registration form). If this is correct, it might help us more easily identify other scenarios in the future.
Note: for organizers sending emails to participants, since the form is JS based, we can simply call the (foreign) API on the event wiki, without redirecting.
@ifried IIRC, you said you were going to read T344441#9365660 and provide feedback, hence moving to product sign-off. Please correct me if I'm wrong!
Below, I have added my perspective. on the original breakdown of whether or not an action requires a redirect, as outlined by @cmelo:
The decisions have been made on which special pages do and do not need redirect, and the next steps for work will be handled in T357793, so I'm marking this ticket as Done.