Some fields in UserRegistration
are obligatory; the country field has a dropdown selection box. Shouldn't the fields in user data form mimic these settings?
Indeed, registration should get its settings from the form...
MC, could you explain that in more detail? There are all manner of possible hidden gotchas lurking in that.
Are you saying that the registation topic should be driven by the user data form?
Even now I see a problem because there is a user data form in %TWIKIWEB% and one in %MAINWEB%.
A field could be mandatory in one and not the other. In fact fields could exist in one and not the other. Ultimately this could confuse the user or even loose critical information. This duplication of control data is a classical bad design.
If you are saying that the mandatory fields should be determined by the user data form and not by whether the names of the fields have a "1" or "0", then there is a different kind of consitency problem. Actually we already have that since the 0/1 mandatory field may conflict with what is deemed mandatory in the user data form in the %MAINWEB%.
Yes I know ... its up to the admiistrator to keep this all straight. But that's poor design, its fragile and that coisistency demand isn't documented as a consistency demand.
I could also interpret your statement as meaning that the HTML form in UserRegistration
is dynamically generated from the user data form in much the same way that
That would be unacceptable to me. I have an extended form, as you can see at http://www.infosecwiki.com/bin/view/TWiki/TWikiRegistration
. The layout is important too. Using HTML for the form gives a flexibility
However, might I suggest that the mandatory fields have a
set in a similar manner to the way the madnatory fields in
- 01 Oct 2005
Deleted my previous comment, as I was completely off the mark (I misunderstood the "requirement".
04 Oct 2005
The more I think about this the more I wornder if all the fuss over the registration form is worth it.
In any non trivial corporate setting the TWikiAdmin
is probably going to customise this.
- 11 Oct 2005
That requires patching the core. The patch is for an old version.
Right now, this only impacts me for the registration form. And the registration form has some fields that are not going into the TWikiForm
Since it only occurs in one place it hardly warrants a generic solution and the overhead of a plugin or having to maintian a separate code branch, which is a drreadful thing to do at the start of a new release sequnce.
If this imapcted a lot of people, if custom form design becomes an issue, then this can be revisited and we can decide whether its worth while as a generic, whether the "database using metadata in forms" becomes a key part of Twiki's functionality (and I hope it does), and wheter this should be integrated into the core -
I suggest this is defered to Edinborough
- 11 Oct 2005
I think you're right - this is a change in UI flow that should be defered -- SD
Undeferred, post Dakar CC
We have removed the country list from the registration form. The only fields left that are mandatory are first name and last name. We can go for consistency or for simplicity. I choose the latter.
- 24 Feb 2012