Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New coaches "saved" but seem to be auto-deleting #484

Open
mUtterberg opened this issue Aug 28, 2018 · 9 comments
Open

New coaches "saved" but seem to be auto-deleting #484

mUtterberg opened this issue Aug 28, 2018 · 9 comments

Comments

@mUtterberg
Copy link

screen shot 2018-08-28 at 5 32 47 pm
screen shot 2018-08-28 at 5 32 59 pm

I've tried to add a coach twice today. Each time, I get a "saved" confirmation, but the coaches section in my admin page shows no coaches and throws me a "no coach with ID ####" error.

@ramonsaraiva
Copy link
Member

@mUtterberg what page is this happening? Also can you provide a step by step of how to reproduce it?

@mUtterberg
Copy link
Author

mUtterberg commented Oct 3, 2018 via email

@ramonsaraiva
Copy link
Member

Thank you!

@bcdickinson
Copy link

bcdickinson commented Aug 30, 2019

I've just hit this issue too. I think the problem is in the CoachAdmin.get_queryset method: https://github.com/DjangoGirls/djangogirls/blob/master/coach/admin.py#L21

It's restricting you to viewing/editing coaches that are already linked from an EventPageContent object for an event for which the user is part of the team, hence the (erroneous) "does not exist" message.

A possible solution would be require adding the coach to an EventPageContent using an admin inline on the creation form. If that sounds like a good idea then I'm happy to create a PR.

@das-g
Copy link
Member

das-g commented Aug 30, 2019

I've just hit this issue too. I think the problem is in the CoachAdmin.get_queryset method: https://github.com/DjangoGirls/djangogirls/blob/master/coach/admin.py#L21

Permalink for posterity:

return qs.filter(eventpagecontent__event__team=request.user).distinct()

@DataCerealz
Copy link

DataCerealz commented May 3, 2021

This issue seems to be still open. I am currently organizing an event and I am running into the same problem.

If someone would drop a workaround as the pull requests don't seem to get approved that would be great.

@mUtterberg it's been a while ago now, but did you manage to get a better workaround?

Otherwise I will see during the next weeks if I can build a little html-boilerplate with inline css or something that can be copy pasted into the admin view form that looks good as a workaround. It would totally force us to add every coach manually in HTML, but it might be the only way for now.

I will post the code here once I am done. This might get others running into this issue a little head start when spinning up their event website.

@vanessa
Copy link
Contributor

vanessa commented Sep 1, 2021

I'll check this.

@vanessa
Copy link
Contributor

vanessa commented Dec 26, 2022

Perhaps this was fixed in #750?

@vanessa
Copy link
Contributor

vanessa commented Apr 30, 2024

There's a possibility that this is related to #956

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants