[TYPO3] FELogin/FEUser-Register and Disclaimers?

[Niels Fröhling]

Hy;

I have a little doubt about the flexibility of the FE-User system in 
general I suppose.
I need to prevent a user to be enabled by "sr_feuser_register" if not 
agrred to terms-of-user. I marked the absend pieces in bold.

1. fill data for new user (create/invite)
2. send confirmation email with shortUrl
3. accept the confirmation
    *do _not_ set disable=0*
    *do _not_ delete the hash*
    *show disclaimer*
    *verify if disclaimer is accepted through POST, _then_ continue 
regularly*
4. auto-login
    *show first-time-login messages [lastlogin=0]*

The agreement MUST happen on confirmation (without validating the user; 
and it can't be as first-time-login message because then all "show at 
login" entries would be usable even if not agreed), because otherwise 
invited users would not need to, instead the inviter would have had to, 
which is illegal.

Problems with "sr_feuser_register":
The hook "confirmRegistrationClass_preProcess" checks no return value, 
so I can't cycle through custom states inside the hook (like skipping 
the validation of the user). Any thoughts? Extending it 'officially'?

Problems with "felogin":
The login-system has a whole seem not to have first-time-login checking 
possibilities. Even though lastlogin may expose that knowledge it is not 
accessible in the moment it could be used (for Typo3 it is a write-only 
field in "createUserSession"), so no way to detect it. It could be very 
easy to have in the very same line a counter "numlogins" or 
"createdsessions", which could at least be fetched and checked for being 
"1". Or possibly an implicit FE_USER-variable indicating 
first-time-login. I don't see hooks allowing me to extract that 
knowledge on my own.
Even more problematic is finding a solution to show content based upon 
the first-time-login check. I'd imagine mining a lot of areas of a 
web-page with contextual help and introduction-text, maintainable by 
editors, and ... (fill in the standard T3-features). It has allready 
much todo with a custom state-system, allowing custom hooks define the 
visibility state of pages and content (the simplest possibility I could 
imagine being "Show at any login (with state-check XY)"). I painfully 
miss that feature every now and then when I want to make complex 
systems; like in this case a "Novice-View"/"Expert View" switch.

Maybe you can give me some suggest how to change my point-of-view, still 
reaching the targeted behaviour.
Thanks
    Niels