[TYPO3-ect] Update on Party Information Framework

[David Toshack]

David Bruehlmeier wrote:
> Hi Peter,
>> I hope we consider taking away all *user* data (name, adress, mail
>> etc) from fe_user and only let it contain *account* data (username,
>> password, login redirects etc) instead...
>>
>> And only have a link between user data (fe_user) and account data
>> (tt_address or PartyInfo).
>>
> 
> that's the idea.
> 
> Greetings,
> Dave.

I know on the wiki page, under the Scope subheader David mentioned that
combining backend with frontend users was out of scope, but I would like
to look at tx_party entities authenticating at different levels of
access and branches of the tree with a view to abolish backend and
frontend users eventually. Do you see this as being a possibility for
the future of tx_party in maybe phase 4? I was thinking along the lines
of the post[1] I made to the ECT newsgroup some time ago.

I would also like to see maybe a tx_party_user extension which would
include the features of all fe_user registration, editing and viewing
extensions. This includes the user features of the community and login
extensions. This of course won't be possible until the tx_party
extension development has levelled out a little, but I just wanted to
drum up some ideas and interest in this project. Even a few +1's or
alternatives would be a great start to gauge some interest.


Cheers,
David

[1]
http://lists.netfielders.de/pipermail/typo3-team-extension-coordination/2006-July/000742.html

-- 
David Toshack - Project Developer - skype: callto://dtoshack
Vaultin - Complete Website Hosting Services
+61 3 9018 7817 - http://vaultin.com