[TYPO3-ect] partner management extension

[Dr. Ronald P. Steiner]

Hi Franz, Hi Andreas,

thanks a lot for the good ideas. So it looks for me as the most 
practical way to use:
1) sr_email_subscribe to allow web page visitors to subscirbe for the 
newsletter. Their data then will be stored in tt_address
2) sr_feuser_register to allow web page visitors to become real page 
users with rights for forum, commenting system, shop, ... Their Data 
then will be stored in fe_users

I'm just confused, as it seems that it might happen that now double 
entries are possible for people who signed in the newsletter and 
therefore are stored in tt_address and who are web page users at the 
same time. How are these two database tables merged?

Subsequent this questions arise:

1) Is there an extension to send a personalized newsletter to both, the 
people in tt_address and fe_users at the same time without sending mails 
double to people?
For e.g. I want to:
- send the newsletter only to people who live in Germany or have no 
place specified.
- address the newsletter recipient with his name if it is specified, 
otherwise just with a "hello"

2) Is there any extension that allows me to view and edit comfortable 
from the back end all data that is stored in fe_users and tt_address at 
the same time.
For e.g. I want to:
- know what information there is for Mr. xy,
- create a entire new person "Mr. xy",
- view all people who live in Germany, (which might be a very very long 
list in my case)
- search for all people who attended a special workshop,
- add the information that someone attended a special workshop,
- update the address for a person
- create a new information field if there was a new workshop and mark 
all people who attended this workshop

3) I want to display some information to some people in the front end. 
For e.g. I want to show all "team members" on one page. I normally would 
use something like "outputyourtable". But now which table do I take to 
get the data from. tt_address or fe_users?

4) What extension would you recommend to import a huge list of 
name<e-mail> in the data base?

I already searched around for a good manual to describe a "best 
practice" for this tasks. But up to now I'm just more confused. There 
are so many extensions and different concepts.

greetings

Ron


Dr. Ronald P. Steiner schrieb:
> Hi List,
> 
> I'm setting up a larger web project and am looking for an extension to 
> fulfill this tasks:
> 
> 1) Storing and checking information of people
> - e-mail, address, name, photo, notes, attended workshop A / B / C / D / 
> ....
> 
> 2) Sending personalized newsletters to people who:
> - live in a certain country,
> - attended workshop A and D but not E
> - ...
> 
> 3) Checking information:
> - who attended Workshop A and C?
> - what information is there for "name x"
> - ...
> 
> What extensions could you recommend for this tasks?
> 
> #### tt_address #####
> The "old" address database. The big advantage seams to me that there are 
> a lot of extensions who base on it. So I could possibly realize a 
> newsletter as required with direct_mail_subscription and direct_mail
> In addition there are lots of interesting extensions which could come in 
> handy later like: rggooglemap, addressgroups, ...
> 
> #### tx_party / wec_people / partner ####
> I am still confused which of this extensions is the most current. David 
> Brühlmeier seems to started with tx_party. Then the "web empowered 
> chruch" carried the concept on in wec_people. partner is now is newly 
> updated by David Brühlmeier again. In general the concept of this 
> extensions looks brilliant. I'm just wondering is one of this extensions 
> a good alternative to tt_address? Which one would you recommend? How is 
> your experience with this extensions? Is there an extension for sending 
> personalized newsletters with data from one of this extensions? Is there 
> a way to use other tt_address extensions with this extensions? Is it 
> worth trying the "new" concept, or is it just a lot of hassle? The data 
> structure of tt_address might be a bit old fashioned, but there are a 
> lot of extensions for tt_address, which might overcome this problem.
> 
> What do you think? What are your experiences?
> 
> greetings
> 
> Ron