[Opensource] update registration problem

[Lirian Ostrovica]

Thanks Mike for the answer.
In fact I thought that you and  the others missed it or something.
If it was something simple, can please you send me the code that made the fix.

There is also something else regarding the update of registration objects.
If you login as a member of extended domain, and try to update Address, Contact, or
Phone you will see that the update does not take effect, while updating Person
works.

Address, Contact, and Phone have two primary keys, while Person has one.

My guess is that the problem rises in runProcessUpdateRecordState  (line 1486) :

   for (Iterator e = db.getKeyFieldListIterator(); e.hasNext();) {
    fieldName = (String) e.next();
    db.setField(fieldName, request.getParameter(dbname + "." + fieldName));
   }
   if (!db.find()) {
    ec.addError("Key fields did not match any record in DB");
   }

interested to hear you opinion

Lirian




Michael Rimov wrote:

> At 12:15 PM 2/12/2003 -0500, you wrote:
> >Hi,
> >
> >The Registration Domain Definitions have a property called "emailValidate"
> >which can be set to 'Yes' or 'No', and another property called 'regRequired'
> >that also can be set to 'Yes' or 'No'.
> >
> >When 'emailValidate'  is set to 'Yes', and 'regRequired' is set to 'Yes',
> >users
> >can register, confirm their email address and logging, but they CAN NOT UPDATE
> >their registration because they get an 'access denied' type of error.
>
> Lirian, thanks for the report.  I've got it fixed in the CVS expresso5-0-1
> branch and it will be part of the 5.0.4 release.  As well as several minor
> UI capabilities to Registration. (Checkboxes, etc)
>
> >Another thing (probably has nothing to do with above) is that I do not
> >understand the practical meaning/use of 'regRequired' property.
> >According to the documentation this property : "determines whether this domain
> >requires the user to go through extended registration or not", but I do not
> >realize any difference whether I set it to 'Yes' or 'Not'. (well beside the
> >update registration issue that I speak above)
>
> I'm not sure how much of an effect the regRequired would have.  But here's
> the idea.  In the older multipage system [and Kris T. is resurrecting it
> for her own use], you could just validate email/password, etc and be
> 'done'... but when you logged in again, if any domain was marked
> "RegRequired", then after you entered your username/password you'd be sent
> to the registration page before you'd be allowed to continue.
>
> I originally moved to single page because if Email Validation and
> Registration Approval were both on, you just turned the system into a
> gigantic pain in the rear to register with: page.. submit... check email...
> click... login... page... submit... check email..
>
> But Kris is making either way optional and I'm all for that.
>
> Thanks for the post and I hope this clarifies!
>                                                  -Mike
>
> _______________________________________________
> Opensource mailing list
> Opensource at jcorporate.com
> http://mail.jcorporate.com/mailman/listinfo/opensource
> Archives: http://mail.jcorporate.com/pipermail/opensource/