+1-888-365-2779
Try Now
More in this section

Forums / General Discussions / Extending Registration Widget in Sitefinity

Extending Registration Widget in Sitefinity

3 posts, 0 answered
  1. Marian
    Marian avatar
    0 posts
    Registered:
    22 Aug 2016
    29 Aug
    Link to this post

    Hello,

    I'm trying to extend the Registration Widget in Sitefinity so that instead of sending the confirmation email to the user, it sends it to an administrator.

    I found this thread: http://www.sitefinity.com/developer-network/forums/developing-with-sitefinity-/implementing-custom-approval-deny-functionality-for-registered-users

    However, I have been unable to get the newly created CustomRegister widget to show in the page designer. It's there in the Toolboxes settings, but not in the designer. Also, trying to change the type of the built-in Registration widget had no effect. I then tried to extend the RegistrationController and managed to get my custom controller to show in the designer, but I cannot use that because the corresponding View cannot be loaded (different assemblies and thus different file locations).

    I have also tried using the Global.asax.cs file to rebind the RegistrationForm class to my CustomRegisterForm class, which also had no effect.

    Can anyone please help?

  2. Victor Leontyev
    Victor Leontyev avatar
    65 posts
    Registered:
    01 Jul 2014
    30 Aug in reply to Marian
    Link to this post
    Hi Marian. Do you want to send email to administrator when someone register in your website? May be you can subscribe to IDataEvent and send email in this handler. More information about that you can find here: http://docs.sitefinity.com/for-developers-idataevent
  3. Marian
    Marian avatar
    0 posts
    Registered:
    22 Aug 2016
    30 Aug in reply to Victor Leontyev
    Link to this post

    Thanks Victor,

     

    what we actually need is to have an extra activation option so that the activation email is sent to the admins so they decide if the user is granted access or not. What we ended-up doing was to extend the registration model (and inject our version on app startup), question now is do we extend the registration view designer (well, actually override) or we add some new property to the application settings... what is considered 'best practice'? :)

     

    Cheers,

    Marian

3 posts, 0 answered