4
Quote:
gtop00 wrote:
Quote:
Most users do not like this though, and to some it is extremely confusing to have this two stage process.
Reply: if it is a module, it can be used or not, according to the admin/site purpose.
What I'm saying is that if you do a two stage process like what I described, then your end users will complain. It's not a matter of how flexible or not the approach is for the admins, it is simply a fact that when users register, they want to submit all their "profile" style information and be done with it. They get very confused when you have to create an account and then fill in another profile form after logging in, especially when the system does not force them to fill in the form (it does not pop up on the screen and refuse to go away until they've filled it in, for instance). The combination of a confusing process, plus no technical enforcement systems, leads to the need to bug users repeatedly to complete the second form inside the system.
Hence our interest in expanding the account creation process.
The biggest stumbling block in my head right now is trying to figure out exactly how to do report generation on the data in the profile. We like having the second registration form provided through Formulize, because we can then generate reports and stats on the info. It's very hard (impossible?) to think of good ways to build an extension to the core that can also be read by the report system in Formulize; the format of data in Formulize is completely different from the format of data in the current user profile system. This might mean that the approach we settle on is ultimately a big hack, rather than true integration to the core.
We have a very long to do list right now, and the changes to the account creation process are not at the top of the list unfortunately. However if there is any chance of integrating them with 2.2, we will need to at least put together a spec sometime soon. So I hope to put out a spec by the end of the month perhaps, but honestly, it's really hard to know when it will happen, and depending on the schedule for 2.2, this might be an improvement that goes into the first release after 2.2, not sure.
And just to be clear, we're not part of the core dev team, we just submit suggestions and patches and such like anyone else.
--Julian