I've been reading all I can in the documentation and forums and feel I'm coming through in some aspects - but becoming increasingly cloudy in others.  So much that I'm rethinking how I may accomplish my registration ---- AGAIN!!

Currently we have 1 paid level subscription - but we also have a Free Registered Users level.

I want users to register - Have Email verified - and then choose to upgrade/purchase/subscribe to the monthly paid subscription.

My current thought/assumptions are to have a plain regular registration form the user fills out - and is sent an email verifiying their registration.  Upon logging in with the verification code - I'm assuming they will be redirected to the "redirect after registration" page I create.

On said page - I can setup another Dynamic Registration form with a checkbox for the user to check if they want to subscribe to the Paid Subscription - and so - if checked - I run through the PayPal registration process and completion events.

I want to streamline the registration as much as possible - but verify emails on the free "Registered Users".

Is this an "optimal" way to achieve this?  Or have I read too much that I'm confusing myself!

Thanks for your input!

You're on the right track, Aj. 

Just a couple of clarifications I'd like to make. 

1. The 'redirect after registration' page occurs right after you hit submit on the registration page and not when they log in.  However, the Dyn Reg w/ PayPal can be set as your redirect page after log in, if you wish.

2.  On the verification codes, make sure you enable your  site to ‘Verified’ under Admin, Site Settings, Advanced. The user registration should be set to verified instead of none, public, or private.

Everything else looks ok, sounds like a good plan to me.

Candace

Candace - thanks for the reply. You've been a GREAT help. But I just want to hit absolute "ease of use" for the end users - so I'm going back and forth.

My idea above is very similar to this thread: http://www.datasprings.com/Products/ProductForums/tabid/727/forumid/3/tpage/1/view/topic/postid/4849/language/en-US/Default.aspx#4849

But I'm definitely not a fan of it. Or having a redirect after login - because a user should redirect to the page they were on in my opinion - and how I'd like it to work for the site.

Now - I feel I'm getting the hang of it - but can't seem to get it working. In a nutshell - I've added a hidden value shortName EnablePGateway and set it's value to "False". I do have Gateway enabled in the settings too!

I have a radiobutton list with two values. A "Free" and "Paid" subscription. I've created 2 Question Events that both fire when a new value in the RadioButtons is selected. When "Paid" is selected - I change the value of EnablePGateway = "True" --- and if "Free" it is set to "False"

My understanding is that if EnablePGateway 's value is "False" it will NOT run through the payment gateway. So I created a "Completion Event" that send a Verification email to the user if "EnablePGateway" = "False".

IF EnablePGateway = "True" ... I expect to go to PayPal and run through those events - and will set up a completion event to automatically verify the user if the subscription is "Paid".

Problem is - even when I have the "Free" option selected in the radio button (the page posts back - which means EnablePGateway should = "False") - and I click Register - it jumps to sandbox.paypal.com

** Also - before this route - you and Chad helped me find my error with the payPal subscription amount. But those tests send me back to my site correctly - but the User is never created - so the new role is never added to them either.

I'm sorry it's a long post. Hopefully it's clear. Any suggestions?

Chad - thanks for the input.  I look forward to the EnablePGateway patch - I think that's the missing link for the Perfect 1 page registration.  Cause if payment is needed or not - it'll find out.  And we can configure the other areas as so.

We all are smart enough to figure out a possible 2-3 step registration - but most users of my websites probably won't take the effort to read and such.

I simply want to email verify the new free users and "pending" paid users - and automatically allow new Paid users.  I figure if they're going to pay - they're probably legit and shouldn't need that added step in registration.

So 3 roads are:
1 - register - pay via paypal - Active paid user of site
2. - register - cancel pay/pending - verify email - free access to site
3 - register - verify email - free access to site.

I'm sure you're already on to that though --- this module is WONDERFUL!!  Core Registration with subscriptions is much to confusing.

I failed to realize betasprings was there to look at.  It sure brings the ideas home for me.

Thanks for everything - sure hop that EnablePGateway is a higher priority fix!

Chad or Candace

I really hate to nag - but I was wondering if there's any "priority level" or possible date for the EnablePGateway value to be working correctly.

Only reason I'm asking is because my client is advertising in 2 major magazine publications and needs everything in place in early
September.

Thanks for everything,

Andy

Hi Andy,

This feature is included in Dynamic Registration 3.2.6.  Please test it out over at betasprings.com.  If it works for you, you can download the patch from Snowcovered.

Good luck!
Candace

OH! That works great!  You guys are GREAT!!!  Thank you1

I'm soo close on my module - just having a couple issues that I don't seem to understand.

I've exported my registration - but cannot seemt to import it into the Dynamic Forms page I created (AJ - The Waka)  I'm not sure where to attach it - but it's in betaspring under root named aj-the-waka.xml

To recap - I have a radio button for a paid user and a free user.  Depending on selection - the EnablePGateway is set to true of false.

Issue #1 - I have an event that is suppose to email the user that their status is pending.  I have it set to the EnablePGateway being False - but for the Free registration - teh user is sent the "Payment Pending" email AND the "Subscription Cancelled" email.  I can't figure out why?

Issue #2: - If a payment is canceled, denied, etc - I still want to create the user - but send a verificaiton email to the email address.  I thought I had it setup as possible - but it doesn't seem to be functioning.

#3 - not so much an issue - just verification - I'm sure I read this - but don't remember where and it's been a LONG day.  On a successful 1 month subscription (billing recurring) the expiration date is set to some some month in 2022.  I'm assuming that PayPal will notify the site to cancel the subscription - and effectively run a "cancel subscription" SQL event I'll run (haven't made it yet - trying to verify the first things).

Is there a way to import the module settings?  There's a LOT to setup to test.

Thanks - Andy

Hi Andy,

I can feel your excitement from way over here.   Let's see if we can clear these other issues for you.

Importing the file -- I see the aj-the-waka.xml file in Admin, File Manager.  However, an xml file like this will not work because the system basically will not know where to put it.  It should be formatted as content.application.yourfilename.xml.  Check out this file on betasprings:  content.DynamicRegistration.aj-the-waka.xml.  You should be able to copy this now anywhere.

Issue #1:  For free registration, try setting these two email events to have the EnablePGateway set to true. 

Issue #2:  I believe this feature works if the payment is pending.  This was just recently added and we plan tol add it to denied and failed IPN's in the next update.  However, this not designed to create a user if the person gets to the paypal page and decides not to proceed (cancel) and there are no immediate plans to add it at this time.  (Of course, a subscription cancellation is a different scenario because assumption is that a user account was already created to begin with.)

Issue #3:  Yes, if your customer cancels the subscription from PayPal, you will receive the Subscription Cancelled IPN.  To this, you can tie an SQL event with this statement: 

DELETE FROM UserRoles
Where UserID = $(UserID)
And ROLEid = 17      ***this should correspond to the specific role id you want to delete.

Let us know how all this plays out for you.

Candace

Candace - thanks for the answers!  I can't believe I didn't catch #1 - it happens when you start overthinking!

This module rocks!!  And so much has improved over the last year + - Keep up the great work --- and THANK YOU for the great support too!

Andy

I think this may be the last of my questions - you have been a great help/asset to me!

I notice on betasprings.com you guys have  "Add Subscriber Role" set to "Completed (Subscription Sign Up)"  --- What is the difference between that and "Completed (Subscription Payment)"  -- it the "Payment" one happening on a monthly basis (if it's a recurring monthly billing?)

Because I'm having one issue - On a successful payment (at least when I know I'm gonna get the money) I want to add the user to a Paid User role.  I have the completion event set for the Subscription Payment.  ALSO, I want to automatically authorize the user - so I have a sql statement to run to set them to verified for Subscription Payment.

** EDIT **
My "set user to authorized" completion event will not run if I have the dynamic field set to "Hidden EnablePGateway" set = to True -- which makes some sense because it's not coming from my form but PayPal.  BUT - it runs for both Free & Paid if I don't have it set - even thought it is tied to a PayPal completion event (Completion (Subscription Payment) 
** End Edit **

I'm going to test for "Subscription Sign Up" but would appreciate a little clarification on the difference between them.

I know I've bee wordy - forgive me.  If a user does an e-check and it takes 3-5 days - is that a subscription "Sign Up"  and then "Subscription Payment' once cleared?

Thanks again!

If you want to have a look, I set it up on BetaSprings.com here: http://www.betasprings.com/DynRegistration/AJTheWaka/tabid/356/language/en-US/Default.aspx

FYI - I didn't change the roles to coincide with the sites roles - so the add users is off.  You want me to fix it?  Or can you get the idea from looking at what I have?

Thanks again!

Hi Andy,

I know, It can get a little confusing.  Here's what I found about those 2 IPN's.  Because the Payment Type is set to subscription, PayPal automatically creates a subscription and makes it active even while the payment is still actually pending.  It will cancel the subscription if the payment fails or if the user actually cancels.

In our initial design, we figured that we (& our customers) wouldn't want registration to complete unless payment has been completed.  However, we found that there many customers who also want their users to get registered even while payment is pending or failed.

In this scenario, you might tie the Create User event to ' subscription sign up'  to just get them registered then assign them paid roles tied to subscription payment.  Otherwise, you can tie all role events to subscription payment.

So, how one uses these IPN's really depends on what they want to accomplish on the implementation and when they want things to happen. 

I hope this helps clear up questions on these IPN's. Meanwhile I'll review your page for the EnablePGateway and will comment on it later.

Thanks for this question.
Candace

Alrighty, AJ, the Waka, here we go.    We reviewed your page and found you generally got it right.  Just need to streamline the process and eliminate unneccessary steps.

1.  The first thing is the 'type of subscription.'  You'll notice we changed the short name to EnablePGateway.  You can think of this as your 'trigger' question.  The way you set 'all access'  to true and 'free'  to false is right on.

So having done that, the hidden field 'enablepgateway' is no longer needed and was deleted.

2.  The event called Assigning Role - Registered User is not needed if you just use the built-in 'create user/update user' event and tie it to subscription sign up.  Then you can add a specific role and tie it to completed subscrption payment.  This way, if the payment fails for any reason, you at least have a 'free' user that can have limited access.

3.  Lastly, any event tied to Paypal must be set to fire on the dynamic field 'type of subscription' on user response - all access (not any field response).  This prevents any events not related to PayPal from firing.  See event called 1Registered -Paid.

So there you go, I hope this helps your implementation.  Thaks!

Candace