Kevin Walsh wrote:
Dan Bergan <suppressed> wrote:Mark Johnson wrote:You will likely need to split this into two operations. Use mv_form_profile to do your profile checks first, and then put the account creation code inside an mv_click. With &fatal in a mv_form_profile, for a failed profile, the mv_click code will never execute. You could, in fact, cut that one profile right between &fatal and the [if ...] line, putting the top part in the mv_form_profile, and the bottom part in the mv_click, and that would be logically the proper division.One more question -- you say the mv_click code will never execute (with &fatal and a failure)... how about mv_check?It's the other way around. The mv_click will run before the profile is checked. In fact, the mv_click callback code can specify the name of the profile to use. The mv_check callback will not be executed if a profile is checked and fails.
That isn't correct in this case, because mv_form_profile is checked very early, before mv_click.
It's very easy to confuse mv_click and mv_check. Someone will no doubt
followup if I have just done so. The following should make it easier:
http://www.interchange.rtfm.info/icdocs/Form_callback_functions.html
Isn't mv_cleanup missing here :-) ? Bye Racke -- LinuXia Systems => http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP => http://www.icdevgroup.org/ Interchange Development Team _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.