Pizzaman
Posts: 19
Posted:
Sep 14, 2004
I would like to have a registration system that allowed for me to specify all data I wish to collect accross multiple pages. For instance.....
If I have a community site that I ask alot of detailed questions... rather than having one long single page we could group our data collection within a grouping of similar or related question per page.
We could have the important signup questions on the first page and if we wanted give the user the option to submit or continue this would happen with button options to submit or continue. if they submit before completing the reg process they can still go back later after they log in and complete the questions. If we have a required section or field on another page then the option to submit on the first page is not allowed and the submit button doesn't show up until they have completed the last required field.
Hope this is considered. I think I asked you about this a very long time ago. :)
Richard Wing
Plumber
Posts: 56
Posted:
Sep 14, 2004
D*mn! i should have thought about this! ;)
----===~~oOo~~===----
// Bjarne Varoytrand aka Black Skorpio
Do to others what you want them to do to you
Unregistered User
Posted:
Sep 14, 2004
Site Admin
Posts: 1320
Posted:
Sep 14, 2004
This is more like a mod in itself like a survey mod where in the end, the user is saved but in the simple user registration.......
At least, not in an easy way I can think of (especially keeping data and the user can come back later).
Chestnut !
Site Admin
Plumber
Posts: 56
Posted:
Sep 14, 2004
----===~~oOo~~===----
// Bjarne Varoytrand aka Black Skorpio
Do to others what you want them to do to you
Pizzaman
Posts: 19
Posted:
Sep 14, 2004
Or a band profile where you are asking a bunch of questions.
The idea was to make the user reg and the profile part of the same process. but if they are busy and cant finish they could still come back and complete it at a later time.
As far as keeping the data.... I meant that the data collected is stored just as if they used the normal reg system. they can always go back in the myAccount and add/edit their info. Thats all I am talking about.
The only difference is allowing us to pick how many pages for the registration process 2,3,4 pages etc..
For each page option there should be a way to create a heading for that registration page that gets placed at the top of that page. The heading could be a category name for the group of questions we are asking them to complete.
Then we build the question (form Fields) and select which page it gets displayed on and if they are a required element to complete.
If the user goes through and views all the registration pages and completes all required fields then the submit button is displayed.
Richard
Pizzaman
Posts: 29
Posted:
Sep 14, 2004
Why not set each form item in a session var? Set/delete each item as needed as the user goes through the various registration pages until the registration is complete. This will also help the user to start a registration, then decide to come back to it later (as long as the session hasn't ended, without having to go through all the items again to enter their desired info).
Site Admin
Posts: 1320
Posted:
Sep 15, 2004
As far as multi-page is concerned, that one will be on hold for the moment as it is too big. When you think about the change in the code, template, even maybe core only to have something that is solid...
There is lot to think about.
Chestnut !
Site Admin
Pizzaman
Posts: 29
Posted:
Sep 15, 2004
Site Admin
Posts: 1320
Posted:
Sep 15, 2004
... sometimes, even a . can confuse Chestnut !
Site Admin