I have an interesting problem when using nf_registration_mod. I setup all the pageroutes and associated them with membership types. The page routes go through 2 nodeprofiles and then have a display link to show what the user has entered. Pretty simple, am using 'lonely node management' as per the directions and the pageroutes themselves work fine. I tested them with an existing user.
However, when I tie them to a membership profile, make it required, and I go through the process of creating a new user account, on the first login after getting password via email, the URL in the browser is the first page of the correct pageroute, but it takes a while to load and then after about 10 seconds, I get a message from my browser that there are too many redirects.
I've tried turning off email verification and the same problem happens: I get the too many redirects page right after the user account creation screen.
I don't think it has to do with my htaccess like mentioned in the following: http://drupal.org/node/141829
The .htaccess file I'm using is the standard drupal config except for the following at the end:
AuthType Basic
AuthName "By Invitation Only"
AuthUserFile /PATH/TO/htdocs/.htpasswd
<Limit GET POST>
require valid-user
</Limit>
I've attached a screenshot.
Any ideas?
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | nf_registration_slashes.jpg | 35.16 KB | jo1ene |
| screenshot_42.png | 26.93 KB | smooshy |
Comments
Comment #1
rconstantine commentedCould you check to see if this is only a problem with Safari? That would help narrow things down. I've never even heard of that error message before.
Comment #2
rconstantine commentedAlso, try it with a standard .htaccess file. That will let you know if it's the module's fault, or your configuration's.
Comment #3
smooshy commentedI get the same problem in FF, slightly different message, but basically the same error:
In IE6, the page just appears to be loading forever. I just had to close the browser window after about 5 minutes.
I tried reuploading the original .htacces and that didn't change the behavior.
Another interesting thing to note. After I get the error, if I just browse to http://site/user, it loads the user page, but there are about 50 of the same error message at the top of the page:
Comment #4
rconstantine commentedI have poked around and have tried to duplicate this problem without success. I suspect it must be a configuration problem with your server, but I don't have any specific advice. If you have any further information that I could use to help you, then please let me know.
Comment #5
jo1ene commentedI have the same issue as described in message #3. I'm not sure that I have any info that will shine light on this.
Comment #6
jo1ene commentedJust s stab in the dark:
I noticed that at /admin/user/nf_registration_mod/ct_adjustments there were missing slashes in the pagroute path. Maybe nothing, just a display error. Or maybe there's a actual malformed path issue. See the attached screenshot.
Comment #7
rconstantine commentedIt's pretty hard to be sure what's going on there. Any way you could turn off your right side blocks and/or use a higher screen res?
Comment #8
jo1ene commentedI realize that the nav menu is in the way. That doesn't mean that the slashes in the paths in the right-hand column aren't missing. I am suggesting that there may be an issue with having more complex paths in the pageroute and maybe nf membership isn't handling them properly. Maybe the output ONLY is fuddled up on this page. Or maybe there is a larger issue.
In my case, there are tree parts: foo/bar[missing slash]too
Maybe foo/bar would be OK
How many parts are in the paths of folks that are having a problem?
I would respond with some more helpful information, as a result of testing, but my webserver is down. Ack!
Comment #9
rconstantine commentedAh, I see. I'll have to check, but is there a reason you MUST have your pageroutes inside a common 'registration' directory? Why not leave that off? If you do leave that off, do your problems go away? I'm not in the office today, so I can't test this myself.
Comment #10
jo1ene commentedWell, I have it working now. All I changed (that should matter) is that I changed the "path" in the page route to be a single part rather than two:
Before: registration/company
After: regsitration_company
Maybe the extra slashes were confusing something along the line. Maybe I'm lucky.
The other thing I did was to page sure that each path had at least 2 pages created. This was to elimiate some weirdness with nodefamily. I am not sure if it made a difference with this problem, but it did clear up a few things.
Comment #11
rconstantine commentedThanks for letting me know. I will look into my path handling and will AT LEAST add a note to the README if it will be a PITA to accommodate non-simple (i.e. regular) paths.
Sorry for the inconvenience. I'll leave this issue open until I decide what I'm going to do about it.
Comment #12
rconstantine commentedAfter further investigation, this seems to be the way pageroutes is designed and not a problem with this module. Pageroutes has the ability to call pages in the route directly as mentioned in its README:
There really isn't any other mention, but I surmise that if users create paths with slashes in them, that pageroute itself may interpret them incorrectly.
As for the display issue shown in the above screen shot, I cannot account for that. What I mean is, this module grabs the value directly from the database and spits it out to the screen without any processing in between - unless I'm forgetting/missing something in reviewing my code.
This further says to me that pageroute simply doesn't like slashes in its pageroute paths.
I'm adding a note to the README to this effect.
Comment #13
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.