Re: What to do about formfield_callback?

Hey James. Thanks for this. Good explanation. I'm sympathetic to the suggestion here, but wary of expanding the Forms API, which already has a number of different ways of holding it. > ...to impose uniform custom widget attributes and error messages across a bunch of ModelForms... My initia

What to do about formfield_callback?

Currently, the ability to set 'formfield_callback' on a ModelForm is undocumented, and a ticket to document it[1] was closed wontfix by Tim with the comment: > The attribute is described as an "internal implementation detail" in #12915 > and the possibility of moving it to Meta is discussed. Ther

Re: Requesting new feature for Django Admin Panel

The packages Django-import-export provides such functionality in a fairly robust manner. Try that. I don’t see a reason to merge too much functionality into the core Django admin, as it will become a maintenance burden. On Fri, 4 Jun 2021 at 16:51, Mohit Gupta wrote: > Hello, > > I'm Mohit Gupta

Requesting new feature for Django Admin Panel

Hello, I'm Mohit Gupta. 3rd year engineering student. I just have a suggestion/idea which if implemented in Django it will be very helpful. As I have faced difficulty in exporting Django admin model data to CSV. I know there is a CLI-based command to export data into a json file format *"pyth

TypeError: Password must be a string or bytes, got BoundField

views.py -- def recruiteRegister(request): error = "" if request.method == 'POST': fname = request.POST['firstname'], lname = request.POST['lastname'], email = request.POST['email'], phone = request.POST['phone'], Pwd = request.POST['password1'], gender = request.POST['gender']