View Article


In the last article, we talked about enabling subscriptions through the inbuilt core facilities. This article will talk about the list of enhancements I will be making as part of the subscription tools module.


While setting up a subscription based site was relatively easy to setup, I have found the system to cause a few management problems and has not been as intuitive as it could be. To address these issues I have been working on a module targeted to help manage and extend the process of selling subscriptions.

Note, this is to sell subscriptions within a single site, not the reselling of multiple portals. That is the realm of an upcoming module called portal tools.

Problem 1: Current Status of a Subscription


At the moment, it’s impossible to tell from my site the current status of a subscription. It might be active or non-active at paypal. This forces a manual check that could be removed. This is not only a pain for the administrator, but your end user would like to know the current status of their own subscription. They can go the membership services section, but it only shows whether or not you are in the role, not that status of the actual subscription at your payment provider (PayPal).

Solution 1: Current Status of a Subscription

Currently when storing a subscription role it only contains two values, the name of the role, and the expiry date of that role.

The solution is to extend the information stored about a role by including a status (possibly separating the role from the actual subscription).

This will be updated when ever a subscription is created (like it currently does), but more importantly when it’s cancelled. (Currently, if you have IPN on, a cancellation actually deletes that person from the role!)

As part of this enhancement, a module showing the status of a subscription will be added, and a reason for that status. This will include links to cancel/join from your site as well. This is to replace the membership services section which is not very prominant.

The question is, it's hard to disable the membership services section, which will still display, regardless if you use another module to do the work. The only real solution is to move the actual subscription away from the role. (So it won't appear in this section). The role will no longer be public and the only way to join the role is through the subscription signup module.


Problem 2: Pending Payments


Pending payments are a problem, when someone pays via eCheck at paypal it can take a few days to clear. As part of this process, they are not automatically added to your selected role. In the current environment, it’s confusing, because the end user does not know what has happened unless they look at your site F.A.Q. Manual intervention is then required to add them to the role.

Solution 2: Pending Payments


As part of the last enhancement, a status field was added to the information stored about the subscription. A status of “pending” will be added to the status field until it clears. When it clears, the status will be update to “active”.


Problem 3: Notifications

The notifications at the moment are not adequate, notifications from your site should be sent whenever an event happens, e.g. created, cancelled and pending.


Solution 3: Notifications

Extra emails will be sent out during the major events in a subscription. These will be customizable like other emails in your portal.


Problem 4: Dev/Prod Payment Gateway


At the moment, there is no way to test payments through your portal.

Solution 4: Dev/Prod Payment Gateway


A facility to supply the URL of your payment gateway, could allow you to test out your site before accepting “official” payments.


Problem 5: Multiple Payment Gateways


Currently, it only supports one gateway. This can be a proper with people that can now pay via paypal.


Solution 5: Multiple Payment Gateways


Add payments to be provider based and configurable.


Problem 6: Reporting


There are no real reporting other then viewing users in a role in “Security Roles”


Solution 6: Reporting


Provide a facility similar to “Site Logs”


These are the problems I have had, have I missed anything?

Posted in: DotNetNuke

Post Rating


Philipp Becker
# Philipp Becker
Monday, May 23, 2005 4:45 PM
Another that I am missing in the core is the ability to add custom membership fields to the users profile and to control different scenarios.

E.g. It is OK for a user to just choose username, password and email address in order to become a member. But then when the user upgrades to become a let's say customer I want to force the user to provide additional information like addresse, Phone, etc...

# Billy
Saturday, May 28, 2005 10:00 AM
James Brown
# James Brown
Friday, June 24, 2005 6:45 AM
I am currently configuring a subscription based site wherin an organization i(as opposed to an individual) is the subscriber, then the ogganization authorizes individuals to access the paid portions of the site. I want to issue an authorization code to the organization which it can issiue to its members and they subsequently would use to register. Can this module handle that?
Laverne Douglas
# Laverne Douglas
Friday, July 1, 2005 8:29 AM
Also excellent. Group memberships have started to be come a problem not just here but and for things like event registration, where an organization will purchase a table for 10, we then have to register 10 individuals under this organization. I like the certificate idea.
Anonymous User
# Anonymous User
Monday, July 4, 2005 5:26 AM
As others have suggested, it would be extremely valuable to be able to register a group, and then specify access to individuals within that group!
Rick W
# Rick W
Saturday, August 5, 2006 6:49 AM
I am new to DNN, so a simple alternate solution might be available, but I need to set up a facility for downloading files specific to the subscriber and viewable only to the subscriber. I considered using a user defined table, but I cannot limit viewing (and downloading) to only the files associated with the subscriber. Any capability in this area would be helpful.

Post Comment

Only registered users may post comments.