Skip to content

Conversation

@Rutvikrj26
Copy link
Collaborator

@kshalot it would be great if you can checkout the PR and point what is going wrong and why the context processors are not passing in the cohostStatus into the templates.

superryeti and others added 15 commits March 15, 2023 11:39
The view will be used by ajax request which will be sent from event_home.html.
Here, when event host clicks the `Make Cohost` or the `Remove Cohost` button,
1. we will immediately disable the button(so that host cant spam the button), it also acts like a feedback to host that the task is processing.
2. Then we send ajax request to our view
3. Depending on the response from view,
 a. If successfull, we will either change the button from `Make Cohost` to `Remove Cohost` or vice versa(depending on whether the host was trying to make cohost or remove cohost)
 b. If unsuccessfull, we will enable the button again to allow host to try again.
Whenever a host adds or removes a cohost to the event, email notification are sent to a) host and b) the added/removed cohost
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants