Forum OpenACS Development: Re: Re: BehaveLikeOutlookP

Collapse
4: Re: Re: BehaveLikeOutlookP (response to 3)
Posted by Malte Sussdorff on 03/18/06 06:55 PM
Carl, wrong commit from testing, so don't worry, removed. As for your direct question:

A) Indeed person::new only makes sense if we use contacts in conjunction with mail-tracking.

B) Not an issue. Code has been written to take this into account (aka: e-mail address already exists in the system as a person but not as a user). But it is not committed as I just overwrote the registration process through a custom package. And this is an issue you face with *every* contacts installation, not only if there are arbitrary e-mails in the system. So we might want to start a new thread and discuss the best behaviour there.

Collapse
5: Re: Re: Re: BehaveLikeOutlookP (response to 4)
Posted by Carl Robert Blesius on 03/18/06 09:23 PM
A) Giving end users the option of arbitrarily adding others to the database might make sense in applications that you are building for specific business clients, but I am having trouble fitting it into how I want to run my sites/applications so I am very happy to see you remove this code from core because there is a danger others will use it as an example. It is also a relief to hear it was test code, b/c it helps me rationalize why you were falling back on naming people using punctuation if no accurate data is available.

B) Happy to contribute to the discussion but I doubt I will be using contacts for any sites I run. It seems it has become a very "customer relationship management" specific package based on the demos you have given me and the discussion I have had with people about it.