User invitations #2095
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-Core!2095
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "user-invitations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #453
added 1 commit
f45574ac- Install django-invitationsCompare with previous version
added 1 commit
caf366a2- Configure django-invitationsCompare with previous version
mentioned in issue #331
added 1 commit
a54a5161- Rewrite templatesCompare with previous version
requested review from @ZugBahnHof
assigned to @hansegucker
added 3 commits
ed2721e3- 1 commit from branch331-user-registration45671793- Merge branch '331-user-registration' into user-invitationsace54cb9- Fix menu itemCompare with previous version
added 1 commit
fbcedb27- Reformat tablesCompare with previous version
I would like that these things can be set using site preferences.
added 1 commit
5da8c609- Rewrite create() method of InvitationModelCompare with previous version
added 19 commits
331-user-registrationa6bf6adc- Merge branch '331-user-registration' into user-invitationsCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
e0d4b550- Use custom invitation modelCompare with previous version
added 9 commits
4120a2c0- Link/Create persons if a matching one is found for a user0b2be5f2- Reverse logic in auto-creation of persons68600351- Validate that the user has a name before trying to create a persond3f6819a- Merge branch 'master' into 332-allow-automatic-linking-of-persons-to-account-by-e-mail-addressc7daea20- Correctly honour auto_create_person preference89e1c037- Update tox.ini; compile messages before building dist2f54f82b- Merge branch 'feature/compile-messages-before-build' into 'master'8911d0e4- Merge branch '332-allow-automatic-linking-of-persons-to-account-by-e-mail-address' into 'master'd6170cc7- Merge branch 'master' into user-invitationsCompare with previous version
added 1 commit
ca4431a7- Add missing migrationCompare with previous version
added 7 commits
75c5a8a1- Enable all panels9f186e6f- Merge branch 'fix-djdt' into 'master'6be1929f- Revert "Support custom authentication backends"d6fe6b89- Merge branch 'bugfix/remove-custom-auth-backends' into 'master'f3e951cc- Always return False for `has_person` if not logged in2190d869- Merge branch 'bugfix/anonymous_user_has_no_person' into 'master'817c894e- Merge branch 'master' into user-invitationsCompare with previous version
added 3 commits
a8f7c79d- Do not link person if anonymous244d300d- Merge branch 'bugfix/do_not_link_person_if_anonymous' into 'master'8078b9e8- Merge branch 'master' into user-invitationsCompare with previous version
added 2 commits
cec255a1- Allow to enter an invitation code in frontend657aee66- Merge branch 'user-invitations' of edugit.org:AlekSIS/official/AlekSIS-Core into user-invitationsCompare with previous version
added 1 commit
cb489f9f- Allow to enter invitation codesCompare with previous version
added 1 commit
971beed2- Fix form fieldCompare with previous version
changed this line in version 19 of the diff
added 1 commit
a2f2870d- Rewrite invitationsCompare with previous version
added 19 commits
331-user-registration8ecd6d44- Merge branch '331-user-registration' into user-invitationsCompare with previous version
added 1 commit
Compare with previous version
assigned to @nik and unassigned @hansegucker
added 1 commit
2b5f9e14- Clean up codeCompare with previous version
added 3 commits
331-user-registration4aea7ffa- Merge branch '331-user-registration' into user-invitationsCompare with previous version
Inconsistent naming — is it for "invite only" or for "signup open"?
Please use the method from the original
Invitationclass.Please use the method from the original
Invitationclass.Should be a preference
Please elaborate a bit more on why this is a custom model.
Should be passed as argument, as this is a generic function.
Please do not add new non-class-based views.
Just redirect to the accept-invite URL here with the entered code.
Please do not add new non-class-based views.
Should list the invitation code
Would be better if it had nice styling for the packs of the code.
changed this line in version 25 of the diff
changed this line in version 25 of the diff
changed this line in version 25 of the diff
changed this line in version 25 of the diff
changed this line in version 25 of the diff
added 1 commit
Compare with previous version
changed this line in version 26 of the diff
changed this line in version 26 of the diff
changed this line in version 26 of the diff
added 1 commit
b566b071- Clean up codeCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
91179e8d- Clean up codeCompare with previous version
I think this is fine from the frontend perspective.
added 1 commit
dff8e2b3- Rewrite form to enter invitation codeCompare with previous version
added 9 commits
331-user-registrationCompare with previous version
added 1 commit
5fc8441b- Merge branch '331-user-registration' into user-invitationsCompare with previous version
added 1 commit
5acbec3e- Calculate number of needed fieldsCompare with previous version
added 1 commit
Compare with previous version
resolved all threads
marked this merge request as ready
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
@ZugBahnHof: Please review and approve
@nik: Please review and merge
added 1 commit
a2d0b930- Redirect to accept viewCompare with previous version
This will show an intermediate page to accept the invite, right? Might be better t obuild the form in a way that filling it in ca ndirectly POST to
accept-invit.Has @ZugBahnHof reviewd this?
Please make this a constant/preference/whatever and use it everywhere.
Magic constant in here… define it somewhere under a readable name.
Also, is this specific to invitations, or not? If yes, name it that way; if not, the block length should be an argument rather than a constant used directly here (it probably should anyway)
I don't think so…
changed this line in version 40 of the diff
added 1 commit
8f6d9e7c- Add preference for packet size.Compare with previous version
changed this line in version 41 of the diff
added 1 commit
c1a5e0bc- Fix redirectCompare with previous version
I don't think this icon is that fitting. Maybe
vpn_keybut that's only a little better. Maybe you find something elseI don't think this icon is that fitting. Maybe
person_addbut that's only a little better. Maybe you find something elseI don't think this icon is fitting here, it is not really submit related
I don't think this icon is fitting here, it is not really submit related
I've seen this now, it's not the most beautiful, but I don't really know how to make it better. But if I remember correctly there is a CSS-class called
hundred-percentinside the mainstyle.scssthat is exactly for this purpose, so you won't need to use this new class.Please use an icon here. Maybe
qr_code?Is it possible for you to write a Layout for this form to make this form be in one line (at east on large enough devices)?
There was a requirement to invite a specific person to register, either by sending that person an e-mail or by generating a code that is only usable by this perosn, and in such a way that the registered user account is linked to exactly that person upon acceptance.
I do not see this implemented in this MR.
added 17 commits
331-user-registration943cda4e- Merge branch '331-user-registration' into user-invitationsCompare with previous version
vpn_key is already used by another official App.
person_addis already used iirc.Which one?
added 9 commits
331-user-registrationb35368bb- Merge branch '331-user-registration' into user-invitationsCompare with previous version
AlekSIS-App-POSIX
yup. Already used by
persons_accounts…changed this line in version 44 of the diff
added 1 commit
aefe0b69- Fix CSS class of buttonCompare with previous version
added 68 commits
331-user-registration3ec87cc7- Merge branch '331-user-registration' into user-invitationsCompare with previous version
changed this line in version 47 of the diff
added 1 commit
26571c48- Rewrite templatesCompare with previous version
added 4 commits
331-user-registration8541e4d4- Merge branch '331-user-registration' into user-invitationsCompare with previous version
added 1 commit
40afdc5b- Rewrite invitation code form to use the same styleCompare with previous version
I still would not use the giftcard icons. Maybe just use some other ones and change them when the new icon set arrives?
And btw, the Core menu section
Accountuses the same icon as the Chronos menu entryMy Planadded 3 commits
91a78776- 1 commit from branch331-user-registrationa1658180- Merge branch '331-user-registration' into user-invitationsCompare with previous version
added 6 commits
331-user-registrationCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
mentioned in merge request !2142
added 5 commits
4a4569ac- Use django-cleavejs instead of django-split-input. Closes #38124fb8afb- Add health checks for media and db backups. Closes #378429d72c7- Use seperate settings for db and media backupd7cf081c- Apply 1 suggestion(s) to 1 file(s)2e0efbdf- Fix syntaxCompare with previous version
added 1 commit
92b72f5e- SicherheitscommitCompare with previous version
added 13 commits
331-user-registrationb566b071- Clean up code09f3dfce- Merge branch 'user-invitations' of edugit.org:AlekSIS/official/AlekSIS-Core into user-invitationsCompare with previous version
added 1 commit
c85c23b3- Merge branch '331-user-registration' into user-invitationsCompare with previous version
added 1 commit
8741335b- [Reformat] Make lint cleanCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
976b1ba9- Reformat templatesCompare with previous version
added 159 commits
331-user-registration6b878fac- Merge branch '331-user-registration' into user-invitationsCompare with previous version
added 25 commits
331-user-registration58ef64dc- Merge branch '331-user-registration' into user-invitationsCompare with previous version
added 1 commit
d2467da6- Reformat importCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
1c333a3d- Fix migrationsCompare with previous version
added 1 commit
993ac84c- Recreate migrationCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
96c06e0a- Move blocks to init methodCompare with previous version
resolved all threads
changed this line in version 72 of the diff
added 1 commit
Compare with previous version
added 89 commits
331-user-registrationCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
mentioned in issue #453
changed the description
deleted the
331-user-registrationbranch. This merge request now targets themasterbranchmarked this merge request as draft
added 755 commits
masterCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 11 commits
masterCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 9 commits
master48a9d143- Install and configure django-invitations1ce516c5- Rewrite invitations modela57092a4- Add migrations2280ba68- Implement invitation logic30677c94- Add helper function to generate random codefb229ce3- Rewrite templatesCompare with previous version
added 1 commit
a409b1ea- Do not create person on signupCompare with previous version
added 1 commit
11fa7752- Refactor registration formCompare with previous version
added 9 commits
masterecfdcad5- Merge branch 'master' into user-invitations6958f79f- Merge branch 'user-invitations' of edugit.org:AlekSIS/official/AlekSIS-Core into user-invitationsCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
a01c02c5- Pass request to formCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
fb0bf2e5- Raise 403 if signup disabledCompare with previous version
marked this merge request as ready
KeyErrors are not for catching.Check for the key in regular flow control, instead.
You should try to retrieve exactly one person here, and error out if none exists.
.last_name, probably.Unrelated change.
Why do we need to reference the person here?
Shouldn't this depend on the preference defined in
preferences.py?This should use
ANY_JS.This manual wrapping seems very questionable, not only, but foremost, because it completely ignores
packet_size.What is it useful for?
Do not use try/catch. Use regular flow control to check for the key.
added 1 commit
3dd56b74- Allow to invite person by idCompare with previous version
We should allow to define two preferences:
Personfields)This probably means we nede to create a
Personobject on registration agian, if one does not exist.changed this line in version 99 of the diff
marked this merge request as draft
changed this line in version 99 of the diff
changed this line in version 99 of the diff
changed this line in version 99 of the diff
changed this line in version 99 of the diff
changed this line in version 99 of the diff
changed this line in version 99 of the diff
changed this line in version 99 of the diff
changed this line in version 99 of the diff
added 1 commit
Compare with previous version
resolved all threads
.
changed this line in version 100 of the diff
added 1 commit
ea616456- Allow to invite specific person on person detail pageCompare with previous version
We need to discuss this again, and look into the different flows for different kinds of invitations.
added 10 commits
master99a2ece4- Merge branch 'master' into user-invitationsf730410e- ReformatCompare with previous version
added 1 commit
5f69250a- Show all available fields of person modelCompare with previous version
added 1 commit
4423231f- Create person on signup if unexisting, allow to edit all person fieldsCompare with previous version
added 1 commit
73453020- Create person on signup if unexisting, allow to edit all person fieldsCompare with previous version
added 3 commits
4423231f- Create person on signup if unexisting, allow to edit all person fieldsb09450da- Fix creation of personCompare with previous version
added 1 commit
9a843fdc- Merge branch 'user-invitations' of edugit.org:AlekSIS/official/AlekSIS-Core into user-invitationsCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
182bb19f- Disallow login if email is not verifiedCompare with previous version
added 15 commits
master4720061e- Merge branch 'master' into user-invitationsCompare with previous version
Please merge the migrations
Should this really be a
Userrather than aPerson?Unrelated changes?
Unrelated changes?
What is this good for?
What if it exists? Where does the data go in that case?
You don't need to call
saveaftercreate.This seems wrong – only users who can invite can accept invitations?
Please re-order, group and unspace.
Same here, see comment above. Please properly group the settings, and what all the empty lines are for si a mystery to me.
Please document how this interacts with allauth and django-invitations (describe the flow, assumptions about upstream behaviour, etc.).
Please document how this interacts with allauth and django-invitations (describe the flow, assumptions about upstream behaviour, etc.).
Please document how this interacts with allauth and django-invitations (describe the flow, assumptions about upstream behaviour, etc.).
Missing docstring.
Please document how this interacts with allauth and django-invitations (describe the flow, assumptions about upstream behaviour, etc.).
Please turn this into a class-based view.
Please document how this interacts with allauth and django-invitations (describe the flow, assumptions about upstream behaviour, etc.).
unn?
jo
mentioned in merge request !2473
added 1 commit
21b67433- Remove unrelated changesCompare with previous version
"Nja lass mal drin"
changed this line in version 113 of the diff
changed this line in version 113 of the diff
added 1 commit
75b3d4a8- CleanupCompare with previous version
added 2 commits
96bce736- Rename rulee657f2f4- Use class-based viewCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
c8626343- Document overriden viewsCompare with previous version
resolved all threads
added 38 commits
masterCompare with previous version
added 1 commit
d8427c77- Merge branch 'master' into user-invitationsCompare with previous version
added 5 commits
master890d2a9a- Merge branch 'master' into user-invitationsCompare with previous version
Why do we have
signup_enabledandsignup_open?We should have
signup_enabledandinvite_enabled(please make sure to check these in all relevant places).The best way forward would be to make the
can_signuprule check that eithersignup_enabledis set, or bothinvite_enabledis set and the user has submitted a valid invite code. This could be done by writing a predecate that checks for a stashed invite in the session.added 1 commit
e52fb507- Use rule instead of preferenceCompare with previous version
What is this method needed for?
Can this be turned into a preference?
Can this be turned into a preference?
Please document, in a comment, what these settings do.
Nein, immer noch nicht.
Nein, auch immer noch nicht.
changed this line in version 121 of the diff
changed this line in version 121 of the diff
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
resolved all threads
added 1 commit
03f0d775- Comment settingsCompare with previous version
This doc string should describe what the class does, not what you did when writing it.
Please use English in the development process.
Please use English in the development process.
Also, please stop marking unresolved threads as resolved!
Also, please stop marking unresolved threads as resolved!
added 4 commits
master860627a5- Merge branch 'master' into user-invitations79554789- Amend changelog for user invitationsCompare with previous version
Follow-up issue: #583
Follow-up issue: #583
changed this line in version 125 of the diff
added 5 commits
master9c872510- Rephrase view doc strings7741f64e- Merge branch 'master' into user-invitationsCompare with previous version
resolved all threads
marked this merge request as ready
mentioned in commit
2a7cc13a4dCongratulations, @debdolph 🎉 !