DynForms 3.0(Love It!!!) DNN 4.9

I am scratching my head with this one.  I am sure someone has done this before.

I am using Dynamic Forms for a user to pay dues for the use of a website.  After payment, they are placed in an Active Role and taken out of the Inactive Role.  However, I want them back in the Inactive Role when the term expires.

My only reason for this is that they will need to be able to be in the Inactive Role to see the link that will use to take them to the PayDues Form Page.

Any Thoughts?  Thanks, Dan

HI, how are you using payment options? Is it with paypal? If so, you could create an SQL completion event to remove them from the Active Role, place them in InActive Role and tie it to Paypal Cancellation and EndOfTerms events. -- David

I am not sure about my logic - maybe I should look at this another way.

Here is the way I am looking at it:

The site has a number of non-paid roles that view limited information.  Everything is members only - no public login.

Non-Paid Roles:  View a limited site based on Role.

Paid Roles:
Member-Active: Views all premium content
Member-Inactive: Does not view premium content; Views Pay Dues module to allow them to pay and enter the Member-Active Role.

Upon a sucessful payment, the uesr is added to Member-Active for 12 or 36 months depending on the payment selected and made.  After the time period has expired, I want the user to revert to the Member-Inactive so that they can resubscribe if they choose and then be placed in Member-Active again upon payment.

The hang up I am having is that I can easily place them in the Member-Active role and remove them from the Member-Inactive upon payment.  I want to be able to pu them back in Member-Inactive when the subscription expires.  12 or 36 months from now.  I do not want for it to be an ongoing subscription that recharges their account on a regular basis.  I want them to resubscribe similar to the initial subscription.

I am displaying PayNow to Menber-Inactive so they know they can get into the Member-Active role with a payment.  Since the Member-Active is only available to some Members (Member-Inactive) and not the other Non-Paid Roles, I cannot make the link to the PayDues available to others - only the Member-Inactive.

Will PayPal subscription feature do this?

I hope this is celar enough to understand.

Thanks, Dan

Edit:  This would work (In my twisted non-programmer mind)

If Role = Member-Active and Member-Inactive then don't display link to Pay Dues

If Role = Member-Inactive then display link to Pay Dues

In this case, I would always leave the user in Member-Inactive and use the Member-Active to restrict them from seeing the PayDues Link.  I thnk this is a feature in DNN 5+ but not in DNN 4.9.  I might be able to use the Show/Hide feature of DF to do this somehow.  I just thought that certainly someone has done what I am seeking to do.

OK, now I'm talking to myself.

I looked at Renewal Reminder.  This will be used as a supplement to what I am doing.

It would be really cool if there was a completion event with renewal reminder that would place the user in one role upon the expiration of another role.

I do have a work around that seems to be a little backwards to me but it does work.

I have a DF that accepts the payment; Adds to Member-Active Role after the payment is made.  The user stays in Member-Inactive (I might rename this to Member-Elegible).

I have a second DF on another page with a single HTML field that contains a link to the Pay Dues page.  The Module is only viewable to Member-Inactive but the HTML field is Hidden to Member-Active.  So, when the user (who is in both Active and Inactive) "views" the module, only the Inactive sees the link as it is hidden to the Active role.

Clear as mud don'tcha think?

I understand that DNN 5 has a hide (rather than view) permissions but I am using 4.9.

Dan

Also, I selected hide submit button until forced visable but it did not hide - so, I deleted all text from the button and it has nothing to display.

Hi Dan,

Your solution actually makes sense (I can see through the mud!).  Generally, creating an inactive role is not necessary since a user automatically loses view permissions once the role expires.  However, since you want to display HTML modules that are only visible if the role is expired, then this should work.

Remember though, that if you're using PayPal, the 2nd instance of Dynamic Forms needs to be visible to all users for it to work.  That's actually a good thing so you only need 1 extra instance to handle renewals -- both for those whose roles are already expired and those who are renewing before role expiration.  Check this thread out for a sample SQL event you can use.

Hope that helps!
Candace