On Monday, May 21, 2012 9:32:04 PM UTC-4, csantos wrote: > > Thanks for the answers. Your suggestion for one single form worked well. > As for the verification issue, it didn't happen when I used the default > user() action (that is, it only happens when I overwrite the register() > action). Perhaps this is a bug? >
It's not a bug -- you cannot do this: auth.register().process().accepted The .register() method already handles the form processing (i.e., it already calls form.accepts()), so by calling .process(), you are re-processing the form. When you re-process the form, it inserts the default value into the registration_key field (which the .register() method has set to a uuid). The .register() method would normally override that uuid insertion, but by calling .process() independently of the .register() method, the insertion is not overridden. If you want to do some processing after acceptance of any Auth form, instead of the above method, you have to register a callback (in this case, you would add an auth.settings.register_onaccept callback, as already noted). Anthony
