I'm sorry to be such a bug.
Just when I got all my pageroutes and everything working, resloved the duplicate account types issue, patched the user module in order to user profile edit page, etc... I don't know what I did, but when I try to register as a new user, I select the membership type, click the "next page" button and the page reloads - doesn't go to the next screen.
Could you please give me a hint what to look for? The first time I had this problem, I noticed that the selections in the box were for old membership types that no longer existed. I deleted the related entry from the variable table and recreated the membership types and reconfigured. Maybe there's something still missing? Per this issue:
http://drupal.org/node/157295
Other than that, I'm not sure what I did.
Thank you for your patience.
Comments
Comment #1
rconstantine commentedNo problem. There are (up to) 5 nf_registration_mod_*** variables in the variable table. Did you delete all of them when you tried to redo things?
Be sure to also clear your cache tables and close and reopen your browser. Oh, and your sessions table too. However, I haven't come across this issue myself, so I'm just guessing.
Comment #2
jo1ene commentedI deleted the few that made reference to the old membership type. I left the instructions setting.
I had previously closed the borwser, cleared cookies and used a different browser. I just now cleared the cache and sessions table with no result.
I guess the next thing to do is wipe everything and start again, unless you have another clue. I just hope I can remember what I did to make it work. Thanks for your help once again!
Comment #3
jo1ene commentedI'm going to cry.
I disabled all the related modules, went through the tedious process of deleting all related variables, deleted extra sessions and the variables cache and started over. Still no dice. Yes. I deleted browser cookies, etc...
Looking through this module suggests that it's only interacting with the accounttypes module (if that...) at the stage where I'm having an issue. I have no idea where to go from here. The pageroutes work wonderfully when I go through them with user 1. Before, I could get the membership selector to work, but the pageroutes weren't working as expected.
As I said, the only thing I really did - to the best of my recollection - was remove all the extraneous nodeprofiles when I realized how much overhead there was.
Comment #4
jo1ene commentedOn login, with a user that I created, but has not gone through the pageroutes, I got this error:
warning: array_search() [function.array-search]: Wrong datatype for second argument in /home/foo/www/modules/contrib/nf_registration_mod/nf_registration_mod.module on line 1028.Hmmm... So I logged back in as user 1 and went to create a new user. I was presented with the membership select and I was able to choose one and create the user. Great! But when I logged in as this new user, I did not have to go through the pageroute, even though the items therein are required.
Maybe a different issue, maybe related?
Comment #5
jo1ene commentedOK. I redid eveything on a clean installation and it works.
There must have been something somewhere that was leftover and/or corrupting something else somewhere else.
Thanks for your help. Best wishes to everyone else. I hope you don't have to reconfigure your whoel site over again like I do.
Comment #6
rconstantine commentedI'm glad you got it working. It's too bad that you don't know why it wasn't working before. There have been one or two other cases reported here like yours, and nobody can tell me what the matter really was. Not being able to duplicate the problem myself, I can only repeat that I'm glad you got it working and hope that some future development I make will squash this bug as a side effect or reveal its nature.
In any case, were you ever using the devel module in trying to locate the problem?
Comment #7
rconstantine commentedLooking at line 1028, the second argument is expecting an array of content types that make up the pageroute for the given membership type. The variable in the second arg is called '$user_pages'. Several lines before, this variable was populated as a subset of the '$all_pages' variable which, in turn, had been filled from the return of the function _nf_registration_mod_get_pageroute_pages(). This function returns an empty array if no pageroute pages are found. I would imagine that taking a subset of an empty array and putting it in the '$user_pages' variable would not result in an empty array, though I've never tested for that. If this is the case, then we can surmise that an empty array was being returned from the above-mentioned function. This then being the case, I would assume a problem with how pageroute pages were defined.
So, it may have been that some kind of problem existed either in the stored data of the pageroute module, or in some reference to it from this module. The only real permanent reference to the pageroute module's data are the items stored in the variables table, which you cleared out several times. So maybe there was a problem with the pageroutes?
That's my best guess for now.
Comment #8
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.