> Not sure about trunk but in newforms-admin at least you can just
> subclass your model field and overwrite formfield() to get the admin
> to use another form field. That way you can declare a custom form
> field (or just a standard one like RegexField) to tweak your
> validation for the forms ge
after digging around in the code, i found "SubfieldBase" at
django.db.models.fields.subclassing
the docs there say this:
"Add SubfieldBase as the __metaclass__ for your Field subclass,
implement
to_python() and the other necessary methods and everything will work
seamlessly."
so i created my ow
> First of all, it assumes you're generating the form manually. What if
> you're using form_for_model, or more critically, using the admin
> interface? Is there a way to specify custom form Field instances for
> a corresponding model Field in the admin?
Not sure about trunk but in newforms-admi
> I understand the preferred method is to create a custom form Field,
> and do validation in its clean() method. However, this appears to be
> lacking in a couple ways.
This can be accomplished at the form level by defining a clean_FIELD
method to clean the data as you see fit. The only time yo
Hello,
As I understand it the model field paramater "validator_list" is now
being phased out with newforms. I'm using newforms-admin, and am in
need of a similar way of doing validation. Are there any hooks or
even hacks available that could achieve this?
I understand the preferred method is t
5 matches
Mail list logo