Active
Project:
Node Profile
Version:
5.x-1.1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 Jun 2007 at 03:21 UTC
Updated:
23 Sep 2007 at 00:04 UTC
When I enable a content type to show nodeprofile fields on the registration page, it breaks the user's ability to register on the site. The fields show up as expected, but when user hits submit, the registration page reloads. In the message area it says the content type was created, but the registration process does not finish. No emails are sent and the account is not actually created. Not showing the nodeprofile fields on the registration page fixes the problem.
I currently have rolesignup, location, and legal modules installed that produce fields on the registration page. I have not disabled any of them to see if the conflict is occurring with one of them. Any thoughts?
Comments
Comment #1
fagopls try disabling location and legal module and make sure you are using the latest nodefamily module.
If this doesn't helpplease report the exact versions of all associated modules (nodeprofile, rolesignup, nodefamily, usernode, drupal)
Comment #2
fagoComment #3
bfbryan commentedI am having the same problem when I integrate the nodeprofile into registration. My site was creating the user but it does not carry the role (using role sign up) and it returns the user to the log in page with this message "Please login to access this personalised page." as opposed to the home page with email instruction message. This message appears to be coming from the 'me' Alias module best I can find. I disabled several modules and added one by one testing. Best I can tell it was a conflict between me alias and node go to module. In node go to you must make sure none of your nodeprofile content types have a path in the the "INSERTING" section. This seems to have fixed my poblems.
Comment #4
fagoso it seems you have fixed the problem, where is the bug? and it doesn't seem to be related to "Nodeprofile fields on registration page break registration" anyway, so it set this back to support request!
Comment #5
abqaria commentedi think i do have a similar error
after upgrading to the newest version of nodeprofile i got error on registration
# warning: Invalid argument supplied for foreach() in /home/iblogger/public_html/modules/node/node.module on line 521.
# warning: implode() [function.implode]: Bad arguments. in /home/iblogger/public_html/modules/node/node.module on line 525.
# user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 query: SELECT n.nid, n.vid, n.type, n.status, n.created, n.changed, n.comment, n.promote, n.sticky, r.timestamp AS revision_timestamp, r.title, r.body, r.teaser, r.log, r.format, u.uid, u.name, u.picture, u.data FROM node n INNER JOIN users u ON u.uid = n.uid INNER JOIN node_revisions r ON r.vid = n.vid WHERE in /home/iblogger/public_html/includes/database.mysql.inc on line 172.
but after unchecking the nodeprofile module the error resolved
maybe because it was removed from registration page
Comment #6
abqaria commentedwell the error was removed into the site, but it is still there
i will try to downgrade the node profile version and see if the error occurs
Comment #7
abqaria commentedi think i am wrong
i did dowgraded the module, same problem
its an error from another module and i cannot figure it out
Comment #8
abqaria commentedthe error appears only when submitting the custom userprofile for the first time
however when updating no error