Not not at all. Sorry didn't realize that not posting it was bad form.
Here's the link:
http://dpaste.com/514877/
On Mar 18, 3:12 pm, werefr0g wrote:
> Hank,
>
> Would you mind posting the link on the list? I may be wrong, but I
> believe that sending a message directly to someone is not in th
Hank,
Would you mind posting the link on the list? I may be wrong, but I
believe that sending a message directly to someone is not in the
"etiquette". You'll also help keeping this list stalker friendly.
Regards,
--
You received this message because you are subscribed to the Google Groups "D
OK I'll start checking stuff then. Even when you have errors on a
screen all of the data previously entered should still be returned
back to the screen with the errors right?
On Mar 18, 2:47 pm, Shawn Milochik wrote:
> Do you know for certain that you're getting past this line?
>
> if request
Do you know for certain that you're getting past this line?
if request.method == "POST" and referer.endswith('upload/'):
Also, you might want to add some logging to your app (or use pdb) to
get information about what's going on at runtime.
Some things I would check:
You have a LOT of fi
OK. It'll be there shortly. I'll send you a note directly once it's
there. Thanks.
On Mar 18, 2:08 pm, Shawn Milochik wrote:
> http://dpaste.com/always works.
>
> I guess the view and the form.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
T
http://dpaste.com/ always works.
I guess the view and the form.
--
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@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsu
Not a problem. Tell me where I can post it and what you'd like to see
and thanks for the help.
On Mar 18, 1:49 pm, Shawn Milochik wrote:
> If you post code I will look at it, but I'm not keen to guess.
--
You received this message because you are subscribed to the Google Groups
"Django users"
If you post code I will look at it, but I'm not keen to guess.
--
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@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubs
In the view for the most part I'm just returning the same screen back
if there are errors, and if there are no errors then it should go to a
completely different screen and just output some messages. Right now
view code is little better than a skeleton, because I just started it
and I'm just checki
What are you doing to the post data in the view?
What are you doing in the form?
If you overrode any clean() methods, did you take care to return the
required value/object?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
The current screen I'm working on has a lot of data on it, with most
of the fields not being required. However it seems like all of my data
gets lost as soon as I submit the screen, even though a lot of the
data does not have any errors, none of the data appears to come back
to the screen for the s
On Fri, Mar 18, 2011 at 12:55 PM, hank23 wrote:
> The order or priority of the fields are not important, but having a
> minimum of at least one is,
If that's the case, then just don't make any of those fields required,
then in the clean() of your form check the cleaned_data to ensure that
at leas
The order or priority of the fields are not important, but having a
minimum of at least one is, so that's why I wanted to save the user
some keystrokes by putting any data input into either field two or
three into field one if it's empty. I'm looking at the form and field
documentation now to try t
On Fri, Mar 18, 2011 at 12:32 PM, Shawn Milochik wrote:
> It's possible to do this by manipulating the post data. It's probably
> cleaner (and more easily reusable) to do it in the form's __init__
> than in the view itself, though.
>
> I don't know what these fields are meant to contain, but assu
It's possible to do this by manipulating the post data. It's probably
cleaner (and more easily reusable) to do it in the form's __init__
than in the view itself, though.
I don't know what these fields are meant to contain, but assuming one
is more important than the others, what if they leave the
Is it possible to move data from one posted screen text field to
another? I have a group of three screen text fields which are
identical in all ways except one. Only the first one is required,
while the other two are optional. So if a user mistakenly enters data
into say field two or field three, w
16 matches
Mail list logo
