On Mar 30, 10:12 pm, "Ian" <[EMAIL PROTECTED]> wrote:
> This situation is greatly helped if the same view displays the form as
> well as processes it. So it could look something like this:
>
> def write_entry(request):
> form = EntryForm()
> if request.POST:
> form = EntryForm(req
; On Fri, Mar 30, 2007 at 03:01:44AM -0700, Helge wrote:
>
> *SNIP*
> > > I wonder if there is a standard way in Django to prevent URLs from
> > > being called directly.
>
> > You can use the require_POST decorator to ensure that the view
> > has some POST d
Hey guys,
Thanks a lot for all your answers!
Helge
--~--~-~--~~~---~--~~
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
On 3/30/07, Arvin Schnell <[EMAIL PROTECTED]> wrote:
>
> On Fri, Mar 30, 2007 at 03:01:44AM -0700, Helge wrote:
> >
*SNIP*
> > I wonder if there is a standard way in Django to prevent URLs from
> > being called directly.
>
> You can use the require_POST dec
> typing it in the URL, I'm getting an error page complaining about
> missing data (which is correct and okay for me, but may possibly seem
> a bit strange for an end user).
>
> I wonder if there is a standard way in Django to prevent URLs from
> being called directly.
it in the URL, I'm getting an error page complaining about
> missing data (which is correct and okay for me, but may possibly seem
> a bit strange for an end user).
>
> I wonder if there is a standard way in Django to prevent URLs from
> being called directly.
That's no
which is correct and okay for me, but may possibly seem
a bit strange for an end user).
I wonder if there is a standard way in Django to prevent URLs from
being called directly.
Helge
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
7 matches
Mail list logo
