-
Notifications
You must be signed in to change notification settings - Fork 13
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
RFC on a changing GuestManager.convert to update in-place #4
Comments
Heya! Thanks for the kind words! What you're describing is exactly how guest users are intended to be used and working. It's possible you may have found a bug where converting will create a new user instead of only deleting the Guest instance? The last line in this test verifies that converting a Guest keeps the User PK |
Thanks very for your reply! I must have something miscondigured on my end, and I'll take a closer look. |
Ah, I see my problems:
Thanks very much for your time and helping me debug from afar ... |
Hi @julianwachholz,
First off, thank you very much for maintaining this package for new versions of Django!
I've opened this ticket to propose a relatively simple change (or addition) of the
GuestManager
in the package that I think would enable greater functionality for devs wanting to create guest users.Background
Business Use Case
I started using this package to enable guest users functionality on a site, with the goal that:
After reading the documentation for
django-guest-user
I didn't see any flags that stated this usage wasn't possible, but after installing the package and trying to use it, to the best of my understanding, the use case above is not supported. I think this has also been raised previously in #3.EDIT:
Thanks very much for your time!
The text was updated successfully, but these errors were encountered: