-
Notifications
You must be signed in to change notification settings - Fork 6
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
✨ #481 - Handle situation where the user has been made inact…" #213
Conversation
… been made inact…""
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that
disabled
param is excessive on the form level: because it the whole form is inactive when why to show itdisabled
param is excessive for the form_action component for the same reason
To be honest I don't understand why to show the form on the message page if the user is inactive?
Let's just remove it from the page without propagating disabled
parameter through several components
Also some testing would be appreciated
src/open_inwoner/accounts/forms.py
Outdated
@@ -245,6 +245,10 @@ def __init__(self, user, **kwargs): | |||
self.fields["receiver"].choices = choices | |||
self.fields["receiver"].queryset = extended_contact_users | |||
|
|||
if disabled: | |||
self.fields["content"].disabled = True | |||
self.fields["content"].widget.attrs["placeholder"] = _("Gebruiker inactief") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
file
field is not disabled
7ca165b
to
fe5b114
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've removed "disabled" parameter from form and form actions.
@JostCrow if it should be present please revert my commit
Restoring PR for 211