Skip to content
This repository has been archived by the owner on Feb 12, 2018. It is now read-only.

External Interfaces

peppertree edited this page Feb 18, 2014 · 7 revisions

There is a setting in the registration module called "External Interface" and this article is about explaining what you can do with that.

Callinf an external interface can help with custom actions that are being executed once a user has registered sucessfully on your site. For instance you may want to auto-subscribe a user to an external mailing list.

In order to make that happen, you have to do some coding. Basically you create a simple class library project and add a single class to your project. The project must have a reference to the Connect.Modules.UserManagement.dll and your class must implement our module's interface like so:

` Public Class AccountRegistrationAction Implements iAccountRegistration

Public Sub FinalizeAccountRegistration(ByRef Server As HttpServerUtility, ByRef Response As HttpResponse, ByRef Request As HttpRequest, objUser As Entities.Users.UserInfo) Implements iAccountRegistration.FinalizeAccountRegistration
End Sub

End Class `

What you can see is that once you have implemented the interface you get access to everything you need to manipulate the user account or the server's response. For instance, after you have taken whatever action on the account, you may want to call Response.Redirect to a special URL, depending on some of the account's data. The possibilities here are pretty much unlimited.

Clone this wiki locally