You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.
Currently, the UI only checks the admin organizations of the user when determining whether editing an event is allowed, or whether events are displayed on the main page.
The API, however, does allow the user to edit suborganization events, but the UI currently doesn't know that, and no such cases have been needed thus far.
This would require some API work to give the UI information on which organization events may be edited, or, preferably, returning user_may_edit or similar boolean in the API per event. This way, UI and API would always be in agreement on which events may be edited.
This would probably require adding a check box in event listing for "Display my own events/Display events in my organization(s)/Display events in all suborganizations", for the main page to remain legible.
Currently, the UI only checks the admin organizations of the user when determining whether editing an event is allowed, or whether events are displayed on the main page.
The API, however, does allow the user to edit suborganization events, but the UI currently doesn't know that, and no such cases have been needed thus far.
However, if need arises,
This would require some API work to give the UI information on which organization events may be edited, or, preferably, returning
user_may_edit
or similar boolean in the API per event. This way, UI and API would always be in agreement on which events may be edited.The text was updated successfully, but these errors were encountered: