-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update Profile Form Issues #16
Comments
The form now posts successfully with changes reflected in the database and the success URL being implemented. Due to the form spanning across both Django's |
The form now pre-populates the current image being used in the custom Bootstrap file field. When the form is instantiated, it displays the image being used according to the model. Upon using the input picker, it displays the image selected from the hard drive. |
The form now GETs and POSTs successfully instantiating the fields as expected. I had to resolve the issue using a function-based view because it was proving challenging validating multiple forms within the At a later stage, I may choose to rewrite the view with a class-based view. I believe it may need a parent class writing too which will include a function that validates multiple forms. |
Correct custom Bootstrap file upload widget
Profile updates successfully. Issue resolved for now. At a later date, an aspirational item may be to change the view from function-based to class-based. |
This Django package may be able to assist in converting the |
Used Django Shapeshifter to use a CBV approach to the Updated tests. |
The form has a multiple form setup involving one for the Django User model and the other a Profile model connected using signals.
There are 3 problems with the form that need to be resolved.
The form does not post successfully
The form doesn't prepopulate for the fields which are from the profile form such as the author view radio buttons.
The form also doesn't pre-populate the image being used in the custom bootstrap file image box.
The text was updated successfully, but these errors were encountered: