Wow thanks, it really works as expected
I've started to write my own patch already :)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegr
On Jan 24, 10:12 am, "Honza Král" <[EMAIL PROTECTED]> wrote:
> see ticket #3257
>
> it is complete patch with tests, the only thing missing is a decision
> whether (and potentially how) to add ( "", "-" ) to choices
> magically if required is False
I believe the ("", "") should go also wh
see ticket #3257
it is complete patch with tests, the only thing missing is a decision
whether (and potentially how) to add ( "", "-" ) to choices
magically if required is False
On 1/24/07, ak <[EMAIL PROTECTED]> wrote:
>
> Adrian, is there any progress on correct handling of foreign key fiel
Adrian, is there any progress on correct handling of foreign key fields
in newforms ? Or could you please give any timeline when this might be
expected to be done ? Even up-to-date svn gives the same error when
trying to save a form with foreign key field.
Also, whould it be possible to do someth
On 1/6/07, Robert <[EMAIL PROTECTED]> wrote:
e = Entry(**form.clean_data)
e.save()
[...]
I'm getting:
Invalid value: 'author' should be a instance, not a error
message when submitting the form.
Hi Robert,
It's telling you that when you create your Entry object, the "
Hi,
I'm having problems with newforms.
my views.py:
from django import newforms as forms
from newforms.ksiazka.models import Entry,Author
from django.shortcuts import HttpResponse, render_to_response
from django.newforms import form_for_model
def add_entry(request):
EntryForm =
6 matches
Mail list logo
