Categories
Bloggers
Blogs RSS feed

A Look at Telerik Sitefinity Customization - Extending Modules to Fit Your Needs

by Tim Williamson

In an upcoming video tutorial that I'm putting together this month, I'll be continuing the theme of extensibility and customization in Telerik Sitefinity.

Here's the story

The Sitefinity forms module allows users to subscribe to be notified when a visitor submits a response. It's a great feature, but if the forms your users subscribe to are frequently filled out, the notifications will start filling up their inbox faster than they can look through them. Even worse, if only a fraction of the responses are actually relevant, the frequent notifications quickly become a nuisance and will drown-out the important ones.

In the upcoming tutorial, I'm going to show you how it is possible to reduce (or completely eliminate) unwanted form notifications by customizing the way they are sent. Taking it a step further, we are going to use the Sitefinity GeoLocation API to give the notifications more relevance by identifying which Sitefinity users should receive them in the first place.

I'll be talking through (and building) a solution to the following list of requirements.

"When a visitor submits an entry through a specified form, a notification should be sent to a custom list of recipients."

"The notifications should be sent regardless of whether the selected users have subscribed to be notified about submissions from that form or not."

"If a user is already subscribed to receive notifications about the specified form, duplicate notifications should not be sent."

"The list that is used should be the one that is geographically closest to the visitor who submitted the form response (based on zip code)."

Even if this isn't something you are working through right now, you’ll be introduced to some pretty powerful customization techniques that can be used and expanded upon in future projects. You won’t want to miss it.

 

UPDATE: The video thing didn't quite work out as planned but there's good news! The code for this has been released to the public and is available on GitHub. Make sure to check out the README near the bottom of the page.

Leave a comment