Common fields during user signup
| Project: | Membership types and registration modification |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Hello and congrats for the great module. I would like to ask the following:
I have three member types (e.g. hotels, restaurants, cars). Each roles should fill in some tabs after login (pageroute). After installing and configuring the module, this works fine.
The thing is, all types have some common fields (e.g. company profile including address, phone etc) that should be completed during the user signup. (along with the username and e-mail).
I understand this was already discussed in http://drupal.org/node/159392 , regarding the "Don't display this nodeprofile on the user account page"., where you instruct us not to check this box. Since this is what i would need, however, could you please provide alternative ways to accomplish this?
Thank you in advance.
#1
The short answer is no. As the README states, if you have common information that every pageroute should have, then you put that on one page and include it in every pageroute.
If you happen to be confused, I'll tell you that all pageroute pages are accessible from the user's edit page. I simply use another mechanism for showing it which is why you must check that box. So set things up, then go to the edit page and notice the link for 'Personal Data' or something like that. That's where the pageroute stuff is.
#2
First of all thank you for your prompt response, I greatly appreciate it. :)
I clearly understood this part of the README file. This is how i did the set up of your module, and i did notice the Personal Data in the My Account -> Edit. Everything works fine!!
The thing is that i need (common) data to be provided by the user during the signup process, not after. This means that a user should first choose a role, and then fill in a form with username, password AND some other fields, according to the role he selected in previous step.
After long reading, i think that this great module of yours cannot be used in my case (unfortunately).... So I was wondering if you could possibly provide any suggestions/solutions. I have been reading and searching for some time now, with no luck....