thanks for the explanation.
En 17 de julio de 2018 1:17:03 p.m. Jonathan Vanasco
escribió:
On Tuesday, July 17, 2018 at 12:45:26 AM UTC-4, jg...@live.com.mx wrote:
so, to make this clear to me: the POST made from javascript is not equivalent
to a POST made in html, the hmtl POST
On Tuesday, July 17, 2018 at 12:45:26 AM UTC-4, jg...@live.com.mx wrote:
> so, to make this clear to me: the POST made from javascript is not
> equivalent to a POST made in html, the hmtl POST automatically refreshs
> page or something like that?
>
This may sound confusing... but their
@steve.percy
i did what you suggest,i passed the params in the query, retrieve them in the
home view and place them in the template, but it is the same. maybe i did not
explained myself: the page does not render at all, it shows "print" message in
the view callable, it shows as xhr in the
@steve.percy
i did what you suggest,i passed the params in the query, retrieve them in
the home view and place them in the template, but it is the same. maybe i
did not explained myself: the page does not render at all, it shows "print"
message in the view callable, it shows as xhr in the
the issue is in your javascript; the browser will never render the template
on this setup.
when you view /test via GET (or missing one or more required POST items),
templates/jg.pt is rendered.
when you view /test via POST with both variables present, the response is a
redirect (HTTPFound)
