On Mon, Feb 8, 2016 at 5:36 AM, Martín Torre Castro <
martin.torre.cas...@gmail.com> wrote:
> If I understand well, you mean that my form templates have to extend the
> main wizard template. Is that correct?
>
> In previous versions this was achieved by writing template_name =
> 'main_wizard_templ
If I understand well, you mean that my form templates have to extend the
main wizard template. Is that correct?
In previous versions this was achieved by writing template_name =
'main_wizard_template.html' into the subclass of WizardView. Am I wrong?
So, with {% extends 'registration/test_wizard.
On Feb 7, 2016 11:46 AM, "Martín Torre Castro" <
martin.torre.cas...@gmail.com> wrote:
>
> James or anyone, the wizard doesn't load the main template for the
wizard, just the first step template form. Can you guess why?
>
The templates you included in your OP didn't have {% extends %} or {% block
James or anyone, the wizard doesn't load the main template for the wizard,
just the first step template form. Can you guess why?
On 7 February 2016 at 02:05, Martín Torre Castro <
martin.torre.cas...@gmail.com> wrote:
> Solved. Silly error. The name for the template function in the wizard
> shoul
Solved. Silly error. The name for the template function in the wizard
should be *get_template_names* and it was *get_templates_name*.
Thank you anyway!!!
On 2 February 2016 at 10:17, Martín Torre Castro <
martin.torre.cas...@gmail.com> wrote:
> Yes, those two templates are both entirely the code
Yes, those two templates are both entirely the code posted.
On 2 February 2016 at 10:07, James Schneider
wrote:
>
>
> On Tue, Feb 2, 2016 at 12:26 AM, Martín Torre Castro <
> martin.torre.cas...@gmail.com> wrote:
>
>> I have DEBUG = True in my settings. When making the request the 200 http
>> co
On Tue, Feb 2, 2016 at 12:26 AM, Martín Torre Castro <
martin.torre.cas...@gmail.com> wrote:
> I have DEBUG = True in my settings. When making the request the 200 http
> code appears. The 500 "Internal server error" code only appears when trying
> to obtain info through the django-debug-toolbar
>
I have DEBUG = True in my settings. When making the request the 200 http
code appears. The 500 "Internal server error" code only appears when trying
to obtain info through the django-debug-toolbar
On 2 February 2016 at 00:06, James Schneider
wrote:
>
> On Sun, Jan 31, 2016 at 2:16 PM, Martín Tor
On Sun, Jan 31, 2016 at 2:16 PM, Martín Torre Castro <
martin.torre.cas...@gmail.com> wrote:
> Hi, James,
>
> I'm trying with the django-debug-toolbar. I can't see anything because the
> message "500: INTERNAL SERVER ERROR" appears. I tried in all the options
> and keeps showing this 500 code mess
Hi, James,
I'm trying with the django-debug-toolbar. I can't see anything because the
message "500: INTERNAL SERVER ERROR" appears. I tried in all the options
and keeps showing this 500 code message.
But it comes to my attention that, for example, the tooltip for "templates"
shows "3 templates re
I can't see the initial load, which is the same as saying that the first
step does not load.
El 30 ene. 2016 1:56 p. m., "James Schneider"
escribió:
> Your view is returning a 200 code, so it thinks it is finishing correctly
> with no errors, probably the reason you don't see any errors.
>
> At w
Your view is returning a 200 code, so it thinks it is finishing correctly
with no errors, probably the reason you don't see any errors.
At what point do you get a blank page? Initial load? Final step? Does the
template in your done() step exist? Have you installed the
Django-debug-toolbar to exami
I'm trying to use the formwizard in formtools package with no success (I
was able to do it when the package was inside Django in earlier versions).
The only response I got is:
[23/Jan/2016 11:06:50]"GET /registration/wizard HTTP/1.1" 200 13729
and a blank page. No errors in browser or Ecli
13 matches
Mail list logo
