Registration question
Last Post 04/09/2014 6:48 AM by Joseph Craig. 1 Replies.
Author Messages Not Resolved
Scott
Nuke Newbie
Nuke Newbie
Posts:7


--
04/09/2014 2:18 AM  
I have a club site for paragliders in my state. Most of my club members conveniently sign up using a PayPal subscription module which creates their account, takes their money, grants the right role, and sends a welcome email. Very nice.

However, occasionally, we would like to allow someone to create an account without going through the PayPal flow, such as when someone pays for a family membership. I would like to have the welcome email direct them to the hidden URL to create family accounts which would then be manually approved by the site Admin.

What I've done is
- Set User Registration = None to hide the Registration link. Members click a "Join or Renew" menu item to register.
- Created a hidden page (not in menu), but accessible by unauthenticated users.
- Dropped a Registration module onto that page.

Expected:
An unauthenticated user hitting the hidden page would see a registration form, and be able to create unapproved accounts which the site admin could manually approve.

Actual:
Unauthenticated users get shown the Login UX, and not the Registration UX. If I sign in and hit the page, I see the Registration UX.

If I change User Registration to any other value, the Register link shows up in the header which I don't want as I want members to use the "Join or Renew" menu item in most cases.

Thoughts on how to fix this or maybe approach differently?

Thanks!

Platform: DNN 7.1.1
Joseph Craig
DNN MVP
Posts:11667


--
04/09/2014 6:48 AM  
Setting the Registration Mode to None suppresses the Registration Link everywhere.

Short of writing a custom skin object, you can suppress display of the register link in CSS with something like this:

#dnn_dnnUSER_registerLink{display:none}

That actually won't make it go away, but someone would have to actively look at it in the page source to undo it.

A better way would be to create a special skin object that does not include the register link, and use that on pages were you don't want registration. Users who know what they are doing could still get there by using http://yoursite.com??ctl=register.

It might be better to keep registration set to none, and write a custom registration module for that special/hidden page. You could copy the stock module, and suppress any checks for registration mode.

You might also want to take a look at Dynamic Forms' Dynamic Login and Dynamic Registration modules. I haven't looked at their features for a while, but they might help.

Joe Craig, Patapsco Research Group
Complete DNN Support


---