Mr. Sykes -

The skin and basic set up for my site, www.immaag.com was done by two 3d parties. The present host for the site appears to have the in depth dnn understanding and set up the site roles/security. I have watched the security role and security role for pages tutorial videos, but remain unclear in my environment about how to allow access to an area for subscribers versus registered users.  

Basically the home page and most content is intended for all users. A registered user is actually captured just to enable meto know something about them and so we can send email alerts when relevant content has been received.

Subscribers are the next level beyond registered user. They not only receive alerts about content via email, they can come to the site and view private, summary data that is  part of the subscription for which they pay. I actually have tow roles, Annual and Monthly that have been set up and do not use the DNN supplied Subscriber becasue I am using Pay Pal to collect subscriptions from the subscribers.  

My problem is that I have set specific pages with either the full content (free to registered users and the public) or the summary data. (meant to be available only to paying annula or monthly subscribers). The public page has two links: 1)goes directly to the full content page that is selected and should be no problem. 2: is a landing page that tells unregistered users to register or unsubscribed, but registered users to subscribe in order to get to the subscriber only information.

However, if they go to the landing page, and register or if they are already registered and go to the subscriber page to "join" and pay; how do I get them to the page(s) that have the subscriber only summaries? I feel I am now the victimn or a circular problem and/or I'm going to have to rethink the entire content area of the site?  

Hello,

Welcome to the forum, ok, I will try my best to help, I have a similar setup running here on DNN Creative.

You are correct to setup 2 new security roles for annual and monthly.

The task is to ensure that the various roles can view the correct data.

The default permissions options in DotNetNuke allow you to setup content to view for:

un-authenticated
registered
'security role names'

The problem is specifying which role can view which content - the problem is that a user in a certain security role is also a registered user.

So, to get around this I have used a module called subscription tools from www.ventrian.com

You add this module to the page and within it you specify the data that the text  / html module will display for each security role.

Here's an example configuration:

A Subscriber Content Page:

Registered user content, "summary of the content"

Security role subscriber, "full article content"

The Ventrain subscription tools also comes with a module for accepting subscription payments, which is what we use on DNN Creative and is much better that the default subscription method that comes with DotNetNuke.

Hope this helps,

Thanks,

Lee