> And this template-code:
>
> This template is the response page when
> the user confirms his subscription(with disclaimer-agreement, prefixing
> autologin or aprove).
>
>
> value="yes" />
> ###LABEL_IAGREE###
>
>
>
This minimalistic variant would suffice, if the confirmation-PID points
t
I patched this into my "sr_feuser_register" for now to solve the following:
> 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
class.tx_srfeuserregister_setfixed
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 wit
