Hi,
What is "form wizard"?
Can you provide a link or an explanation, example?
On Tuesday, April 11, 2017 at 9:29:39 AM UTC-4, Pranay Verma wrote:
>
> Hi
> Is there any way to use form wizard in Django 1.10 ao above
>
--
You received this message because you are subscribed to the Google Groups
"
Solved with a very easy approach.
I override the WizardView get method and I use a session variable to
understand if the user want to restore the edit or create a new form
def get(self, request, *args, **kwargs):
"""
This method override the WizardView handling the restore of t
I'm trying to get the data from the session. The SessionWizard store the
data in the session
session_data = request.session[wizard_key_form]['step_data']
at this point session_data is the dictionary with the data in the form
filled by the user.
But this doesn't work
ServiceCreationWizard.as_vie
On Fri, Feb 20, 2015 at 5:49 AM, Collin Anderson
wrote:
> You could instead just override get_form_instance(step). That way you'll
> have access to self.request.
>
Thank you!
--
Karim N. Gorjux
--
You received this message because you are subscribed to the Google Groups
"Django users" g
Hi,
You could instead just override get_form_instance(step). That way you'll
have access to self.request.
Collin
On Tuesday, February 17, 2015 at 8:26:30 PM UTC-5, Karim Gorjux wrote:
>
> Hello mates!
>
> I have some problems to understand how to set the view for
> the NamedUrlSessionWizardVie
On Wednesday, July 13, 2011 4:31:58 AM UTC+2, Dario Vergara wrote:
>
> Here is the solution:
>
> def get_template_names(self):
> next_step = int(self.steps.current)
> return 'step_%s.html' % next_step
>
>
> Simple solution. What is confusing is that the documentation says
for anyone having the same problem:
https://code.djangoproject.com/ticket/19285
--
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
d
>Separate step is separate browser interaction. Even if you did this with
>AJAX, other requests can come in in between actions. Other users don't get
>blocked from accessing the site just because one is in the middle of
>registering. Sorry, but that's the way the web works.
>
>By the way, you do
On Tue, Nov 13, 2012 at 9:07 AM, azurIt wrote:
> >You really need to create the account, thus reserving the login
> (username?)
> >in step 1, when the check succeeds (in fact, the test probably should be
> >an attempt to create the account, whose failure is what kicks the user
> back
> >to choose
>You really need to create the account, thus reserving the login (username?)
>in step 1, when the check succeeds (in fact, the test probably should be
>an attempt to create the account, whose failure is what kicks the user back
>to choose another login). You keep a creation date and note (perhaps
On Tue, Nov 13, 2012 at 8:17 AM, azurIt wrote:
> Hi,
>
> i have the following problem:
> User is choosing a login in first step (login is validated and is checked
> if it's available) and is filling up some other data in second step.
> Finally, i'm trying to create a new account BUT the login can
Hi @mtnhiker.
I ran into very similar problems and spent weeks dealing with a View class
based on Django-1.4's
django.contrib.formtools.wizard.views.SessionWizardView. It was so much
customization that some things started to go wrong and debugging was awful.
I came up with this solution:
https
Answering my own question...
I debugged my brain a bit and got something working with branching. Here's
my interpretation of my brain bug.
First a "step" is not something attached to a particular form. Its the
index in a sequence. The same form might be step 2 with one branching
structure b
Does anyone have any advice please? :)
Thanks,
Leandro
On 7. juli 2012, at 02:33, Leandro Alves wrote:
> Hello,
>
> I'm starting to use Django now and I would need some orientations in order to
> create a Form Wizard.
>
> The idea is simple:
>
> The first form will contain only one field
Here is the solution:
def get_template_names(self):
next_step = int(self.steps.current)
return 'step_%s.html' % next_step
Simple solution. What is confusing is that the documentation says that
get_template_names() should return a list.
--
You received this message because y
The documentation
on https://docs.djangoproject.com/en/1.3/ref/contrib/formtools/form-wizard/
is pretty clear. The part where you're going in the wrong direction is the
url config. Compare
with
https://docs.djangoproject.com/en/1.3/ref/contrib/formtools/form-wizard/#hooking-the-wizard-into-a-u
On Fri, Aug 14, 2009 at 4:17 PM, Dustin wrote:
>
> Looks like you're not implementing the done() method required in
> FormWizard sub-classes.
> http://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/#creating-a-formwizard-class
It actually ended up being my CodeWidget being wonky,
Looks like you're not implementing the done() method required in
FormWizard sub-classes.
http://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/#creating-a-formwizard-class
On Aug 14, 11:29 am, Adam Olsen wrote:
> I've got a FormWizard with two forms in it. It validates the firs
So that's how that works. Brilliant. Thank you. It worked perfectly.
On May 19, 1:43 am, George Song wrote:
> On 5/18/2009 4:01 PM, geraldcor wrote:
>
> > Hello all,
>
> > I am working on my second Django app and it involves a very long form.
> > I successfully used modelForms in my last app to
On 5/18/2009 4:01 PM, geraldcor wrote:
> Hello all,
>
> I am working on my second Django app and it involves a very long form.
> I successfully used modelForms in my last app to successfully save
> form data to a database.
>
> With this long form, I have split it up into smaller forms (forms.For
Thanks, will do that tomorrow.
Kirill.
On 14 апр, 00:14, Adi Sieker wrote:
> On 13.04.2009, at 21:43, Kirill Zaborski wrote:
>
> > So no answers were given and I tried to fix FormWizard class.
> > The patch is attached and the only thing changed is that the
> > revalidation is made with forms
On 13.04.2009, at 21:43, Kirill Zaborski wrote:
> So no answers were given and I tried to fix FormWizard class.
> The patch is attached and the only thing changed is that the
> revalidation is made with forms which were before the last one (I
> do not see any reason for the second validation
Thank You Elliott.
regards.
On 6 Kwi, 11:52, Elliott wrote:
> On Apr 5, 4:24 pm, eli wrote:
>
> > No, how to add functionality to back to the previous step without
> > deleting current step's data.
>
> > regards.
>
> That can't be done with the current form wizard. A session-based
> formwizar
On Apr 5, 4:24 pm, eli wrote:
> No, how to add functionality to back to the previous step without
> deleting current step's data.
>
> regards.
That can't be done with the current form wizard. A session-based
formwizard that would have allowed this was on the list for django
1.1, but nobody real
No, how to add functionality to back to the previous step without
deleting current step's data.
regards.
On 5 Kwi, 22:39, codecowboy wrote:
> Are you asking how to modify the html in the multi-step-form app to
> add a button?
>
> On Apr 5, 4:33 pm, eli wrote:
>
> > No, I have one view.. My ex
Are you asking how to modify the html in the multi-step-form app to
add a button?
On Apr 5, 4:33 pm, eli wrote:
> No, I have one view.. My example is similar to that one from Django
> tutorial:http://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizar...
>
> regards.
>
> On 5 Kwi, 21:
No, I have one view.. My example is similar to that one from Django
tutorial:
http://docs.djangoproject.com/en/dev/ref/contrib/formtools/form-wizard/?from=olddocs
regards.
On 5 Kwi, 21:52, codecowboy wrote:
> Do you have one view for each form or do you use one view with a large
> amount of co
Do you have one view for each form or do you use one view with a large
amount of conditional logic (e.g. if stepone then show this form
elseif steptwo show this form)?
On Apr 5, 1:14 pm, eli wrote:
> anybody ? :-)
>
> regards.
>
> On 4 Kwi, 11:17, eli wrote:
> I have no problem reading existing
anybody ? :-)
regards.
On 4 Kwi, 11:17, eli wrote:
> Hi,
>
> What is the best way to add button "previous step" to multi-steps
> form ?
>
> Thank You.
>
> regards.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"D
There's a ticket for a formwizard that will rely on sessions rather
than POST data (http://code.djangoproject.com/ticket/9200) but it
doesn't appear that anyone's working on it at the moment. If you
really want to see this happen, your best bet is to read through the
ticket and pick up work where
Maybe i don't have exact solution to your problem, because i've never user
form wizard so far. I always create my own forms. During user's registraton
process i save user.id in session and in every view i'm testing if this ID
is in session (it menas, register process has not been finished) and if
anyone?
--~--~-~--~~~---~--~~
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+unsubscr...@
It seems to me like a quite simple requirement for a form wizard ...
but I'm still unable to find a simple way to do it ...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group,
Perfect !
Then i just do a {% ifequal request.GET.extra_context "foo" %} and it
works.
Thanks
On Jan 16, 3:10 am, Malcolm Tredinnick
wrote:
> On Thu, 2009-01-15 at 04:13 -0800, coulix wrote:
> > Hi,
>
> > I use a formWizard for a signup process:
>
> > url(r'^signup/student/$', SignupStudentW
On Thu, 2009-01-15 at 04:13 -0800, coulix wrote:
> Hi,
>
> I use a formWizard for a signup process:
>
> url(r'^signup/student/$', SignupStudentWizard([SignupForm,
> StudentForm]),
> {'extra_context':{"type":"student"}}, name='signup_student',),
>
> Now, used as it is it works fine.
Maybe I'm experiencing this?
http://code.djangoproject.com/ticket/8808
I don't even understand what that ticket is about. And I'm not using
parse_params or get_template...
On Sep 3, 4:06 pm, lingrlongr <[EMAIL PROTECTED]> wrote:
> I'm desperate here. I'm having serious problems with the form
On Wed, Jun 4, 2008 at 6:31 PM, tyman26 <[EMAIL PROTECTED]> wrote:
> Unless I am really mistaken, I am pretty sure this is a bug. The
> "self.step" variable in "wizard.py" is never being updated after the
> forms are submitted. These are two possible fixes I found:
This is a known bug already,
Unless I am really mistaken, I am pretty sure this is a bug. The
"self.step" variable in "wizard.py" is never being updated after the
forms are submitted. These are two possible fixes I found:
1. In the method "def __call__(self, request, *args, **kwargs) :"
update the self.step variable after
38 matches
Mail list logo
