I'm using rolesignup to have users select their role at registration. The problem is, after the first step of your module (selecting membership type), they are directed to choose their role (from rolesignup), then username and email(first step of registration) but after that the process ends. They don't get directed to the pageroute.
How can I preserve the functionality of your module? (You think you can take a quick look at the rolesignup module? It's only 6 functions or so, like 100 or less lines of code).
I tried editing it myself, but I just succeeded in having the registration stuck on one page (submit redirects to same page).
Comments
Comment #1
rconstantine commentedBefore I look at any code I have a quick question for you. Do you require email verification or the admin to authorize sign-ups? If either is true, then registration will end where you say it is and the user won't be able to fill out the pageroute until they return to the site after the above conditions are met.
Comment #2
zahor commentedNo, email verification is not required but usually the registration works fine with email verification required and doesn't when it is isn't but I'm not really worried about that part.
Comment #3
rconstantine commentedWait, you lost me.
First, without the rolesignup, does my module work as expected with the email verification set to what you want it to be? What is that setting?
Second, with that same setting, are you saying that my module breaks when you add rolesignup to the mix?
Comment #4
zahor commentedWhen there is no email verification, the module doesn't function as it should. Right after choosing username/password, the user is directed to the front page. Same thing happens with rolesignup.
So the workaround I chose before rolesignup was to use pageroutes to redirect users to a page 9after filling out profile) instructing them to go to their email address to verify their account. On the second instance, they are redirected to a CiviCRM signup page to add contact information based on the type of membership they have. But again, I'm not worried about that, since I have a workaround for it.
The problem I was having was that users were not getting the roles for the particular membership type, hence rolesignup, but now they aren't being allowed to fill out the profile.
Comment #5
rconstantine commentedSo it sounds like this is really a bug report.
I need to fix it so:
1) when not using email verification, users fill out their email, username, password, etc. and are then routed to the proper pageroute.
2) the message to check their email when verification is required is preserved so they know to actually check their email
One last question for you: with email verification enabled, after the user checks their email and returns to the site, they should be directed to the proper pageroute. Are they?
Comment #6
zahor commentedWith email verification enabled (without rolesignup), they can complete the registration just fine. It's just that at the last page, they are not told that they have to check their email,but just get a "You are not authorized to access this page" message. It's not such a big problem.
When they return to the site, they are taken to their user account.
Which reminds me of another problem! . The profile page says "this user has not filled out a profile" even when there is a profile. You can click on "edit profile" and see it, or click on the pageroute name in the menu and see it. So I just checked "display this nodeprofile on profile page" - the option you said to uncheck.
Any luck with making rolesignup not interrupt the pageroute?
Comment #7
rconstantine commentedFirst, when I register as a new user, I get the following messages when I complete the username/email page:
So I'm not sure why you aren't getting the notification to check email like I am.
Second, when you say
, do you mean that if you visit a user's page such as user/5 that you get this message? My module does not generate this message. You might have the standard Drupal module 'profile' enabled which you should not have done. Actually, I just did a quick search and I can't figure out which module produces this message. Is that a direct quote?
Third, I haven't yet finished with the other project I'm working on so I haven't gotten a chance to work on fixing this or any other issues for any of my other modules lately. I'll get to them soon.
Comment #8
zahor commentedAny updates with preserving registration pageroute? Or should I try to find another solution?
Comment #9
rconstantine commentedBecause your original message said that you needed the preservation of the redirect for use with rolesignup, and I have now implemented auto-role-assign based on membership types, I'm going to call this good.
Also, there should be a place that you can specify a URL for after the completion of a pageroute in the pageroute settings. See the screenshot at #21 here: http://drupal.org/node/167674.
Also, you'll notice in another post elsewhere that I mention that the user will not follow the actual pageroute during the registration process but will fill out the pages of the pageroute.
Also, I mentioned that only REQUIRED pages will be enforced. Otherwise the user doesn't have to fill out anything and won't get sent to the pages of the pageroute at all. They can fill out the pages at their leisure from their user profile's edit page, but nothing is required unless marked REQUIRED in the nf_registration_mod settings.
If there is still something that these answers do not address, please open a new issue.
Thanks.
Comment #10
(not verified) commented