Bug #7391
custom user fields empty on profile page
Start date:
27 May 2015
Due date:
% Done:
100%
Estimated time:
Patch proposed:
Yes
Planning:
Description
Even if in database there is a value for a custom field, the profile form shows it empty and doesn't save the new entered value
Files
Associated revisions
History
Updated by Benjamin Dauvergne almost 6 years ago
Serghei, to finish you could add a test for the profile edit page.
Updated by Serghei Mihai almost 6 years ago
- File 0001-tests-user-profile-edit-with-custom-attributes-7391.patch 0001-tests-user-profile-edit-with-custom-attributes-7391.patch added
- Patch proposed changed from No to Yes
Here is a test checking the editing of custom fields.
It should be merged with the one proposed in #7386. I can manage that
Updated by Serghei Mihai almost 6 years ago
- File 0001-forms-if-not-form-class-is-given-to-modelform_factor.patch 0001-forms-if-not-form-class-is-given-to-modelform_factor.patch added
One patch combining the two previous
Updated by Benjamin Dauvergne almost 6 years ago
- Status changed from Nouveau to Résolu (à déployer)
- % Done changed from 0 to 100
Appliqué par commit authentic2|6786b2529d35f81d8c90068871a24db4186f93db.
Updated by Benjamin Dauvergne about 5 years ago
- Status changed from Résolu (à déployer) to Solution déployée
forms: if not form class is given to modelform_factory() on User model, user BaseUserForm (fixes #7391)
Building of the base classe tuple has been refactoed.
Bug introduced in 7141a96e6