Help a struggling student please!

rconstantine,

Thanks for the reply.

If I understand you correctly, it sounds like your module doesn't use the standard registration screens that drupal serves up ordinarily.

I had used PROFILES to create my registration fields. Was this incorrect? Should I delete those fields, and instead use CCK (which I have not yet installed, but will try out shortly) to create the registration fields?

-David

Hi rconstantine,

Thanks for your followup note. You are correct: I did not read all the documentation for all of the required modules. I found your module first (it was the one that I was interested in) and then downloaded all the additional required modules. I assumed that the documentation for nf_registration_mod would cover everything I needed to know in order to get the module working. That has generally been the case for all the "simple" modules that I had installed prior to that.

nf_registration_mod is a much more complex module than the other ones I have used. I am guessing that your documentation is easier to follow once a user has a good working knowledge of all the other required modules such as nodeprofile. For me, it was kind of a "chicken-or-egg" dilemma. Which module should I try to understand first? Since your module was the one that I was really interested in using, it was the one that I tried to learn first. After that didn't work, I tried to take a stab at pageroute, but was equally flummoxed. Then I simply gave up.

I am going to give it one more try, and I'll let you know when I get stuck!

Here are your instructions, along with the steps I've taken or questions I have:

--SETUP/INSTALL--
Before you activate this module you should probably do these things:

1. Install the nodeprofile module. DONE.
2. Install the pageroute module. DONE.
3. Outline the membership types you would like to have and the data you would like to collect from each group of users. Identify which fields are in common and which are not. When you say OUTLINE, I assume you mean simply "on paper" or "in your head". In my example, I have three membership types (Student, Parent, Other) and a list of fields that are in common and not in common.
4. Identify which fields you would like to require, and which you don't. When you say IDENTIFY, I assume you mean simply "on paper" or "in your head". I have done this.
5. Create the content types based on your observations in steps 3 & 4 such that you minimize the number of pages, but separate required/non-required, and common/non-common items. This may result in one or more content types with only one field, depending on your situation. That's okay!!! With the pageroute wizard system, it really isn't important to jam a page full of fields, and in my opinion, looks cleaner anyway. I created two content types (so far): reg_common (for registration info common to all membership types) and reg_parent (for registration info common only for parents).
6. Make sure you've setup your roles and permissions how you want them. If you use the accounttypes module, you will keep in mind to make roles more granular than you might otherwise. If you'd like to use the accounttypes module, enable and set it up at this point. I am going to hold off on using accounttypes until I have mastered everything else. When I played with accounttypes previously, I nearly made it impossible for myself (the admin) to log in!
7. Copy the module's files into your site's module folder per standard Drupal practices. DONE.
8. Enable it at the module administration screen. DONE.
9. There is no install file as no database table needs creation. The standard variables table is
   used for global settings and user data is stored in the user's 'data' field.

So can you outline what my next steps are?
What should I use next: noteprofile or pageroute?

Any guidance would be appreciated! I think I am on my way to figuring this thing out! Thanks so much for your continued assistance!

Warmly,

David

The step 3 in the usage section of my readme file actually does say "Here, I unchecked the 'Integrate this node profile with user categories.' box." Perhaps you already fixed the copy?

I will leave the box unchecked, unless you let me know that I have misunderstood somehow.

Another quick question: you mentioned in a previous post that I should not use the Profile module. This module is required by two other modules I am using: AdSense (enabled) and Contact real name (enabled). I guess I could do without contact real name module, but I would like to keep AdSense if possible. Is it necessary to disable the Profile module?

An additional question:

In your usage section you write --

4) Next I worked on the pageroutes at admin/build/pageroute. First thing I did there was create the routes at admin/build/pageroute/add using the 'add route' tab. I named the path [What do you name the path? Can it be any name I want, such as "register"?], then deselected the workflow option [I don't see a "workflow option". I see four options in the advanced settings. Do you mean "Don't show drupal messages during this route."?], selected 'Show tab-like submit buttons above the page content.' [DONE], assigned the appropriate roles to it [I selected "unauthenticated user" since they are the only ones registering. Right?], selected one of the PAGE1's for the nodefamily head, set the 'Customized redirect' to user/!uid, and checked 'Preserve destination parameter during this route.' [I skipped this part since for now I am not using nodefamily since my needs are simpler] I recommend that you name your pages the same as the human-readable names of your content types. The reason is that this module gives a list of required pages to the user and it is nice if profile category links match pageroute submit-tab links. [Again, I skipped this part since for now I am not using nodefamily since my needs are simpler]

Thoughts?

Sorry to be so dense...I just can't seem to get this working.

OK...here is where I am at.

Page Not Found
When a new user registers, and clicks submit (or whatever it says...), they then get Page Not Found.
They still get the confirmation email, so the registration is successful, but they get the Page Not Found error at the end of the registration process. What setting is screwed up for this?

Then, when they log in for the first time, they are brought to their User page (such as user/4). I imagine they are supposed to be brought to the start of the pageroute stuff. Where should I look?

I feel so close...but so far. Maybe someday I can get this to work!

rconstantine, you are a saint for hanging in there with me. Thank you!

Let me try this without screenshots first, and see if I can give you enough info. If not, screenshots it is...

1. After hitting "submit" when registering, the user is taken to the following URL where they get a "Page Not Found" message: http://team8w.com//0/5
2. After hitting the email verification link, the user is brought to this page: http://team8w.com/user/5/edit, where they can create a new password. At the top of the page in red is the following error: warning: Invalid argument supplied for foreach() in /home/teameigw/public_html/sites/all/modules/nf_registration_mod/nf_registration_mod.module on line 887..
   The new password is accepted and the url remains http://team8w.com/user/5 with the message "The changes have been saved".

   Off to put the kids to bed...let me know if this means anything to you!

   -David

OK...I have started with a cleaner installation of Drupal 5.2, on the premise that some other modules that I had previously added are causing a conflict of some sort. This new installation isn't completely virgin, but it's close enough.

A quick question:
Should the Pageroute Nodefamilies module be activated? See attached screenshot.

Now that I have a clean installation, I did the following:

• Created Content Types (Common Registration, Student Registration, Parent Registration)
• Created two Page Routes (student_reg: goes from reg_student to reg_basic. parent_reg: goes from reg_parent to reg_basic).
• I set up nf_registration_mod with two roles: Student connected to student_reg pageroute, and Parent connected to parent_reg pageroute.

I next attempted to register as a new user, and was prompted to select my role (Student or Parent). So far so good! I selected Student, entered my username and email address, and clicked submit. Then I was taken to /student_path/0/3 which gave an Access Denied message.

Then I received the confirmation email, and clicked on the link, which brought me to /student_path/reg_basic. Two problems: 1) Unfortunately, I once again got the Access Denied message. 2) Shouldn't the pageroute have taken me to the first page in the route, reg_student? See the attached screenshot.

I think I'm making good progress, and may be only one setting away from getting this to work!

Let me know...

-David

Getting down to the last few details...I hope.

After filling out the standard Drupal registration form, and clicking submit, a "virgin" installation takes you right back to the homepage, where everyone has authorization to view it.

In my development site, where I have tried to implement your module, the user is taken back to /student_path/0/3 (or similar path) instead. Can you point me to the setting or checkbox that is making this happen? It is crucial that they be brought back to the homepage, because they have not yet received the confirmation link, and therefore receive a Access Denied message.

I don't have a good code editor, so I can't determine which line is 1091.

Is there text I can search for to give me a direct hit?

Otherwise, I'll have to wait until I can download a good code editor, or wait for an update on the module.

Thanks for all your help!

-David

OK. I realized I had a code editor afterall.

I changed the following line 1091 in the nf_registration_mod.module file--

From:
} // function nf_registration_mod_submit_intercept()

To:
return '';
(those are two single quotes.)

Unfortunately, this is the error I got:
Parse error: syntax error, unexpected $end in /home/teameigw/public_html/dev/sites/all/modules/nf_registration_mod/nf_registration_mod.module on line 1287

Did I modify the wrong file?

Basic issue is resolved. Bug moved to a separate bug issue. Closed.