Hi,
I´m implementing this module in a social network like site (petlove.eu). I´m currently testing, testing and testing...
I only have one profile type node. Could i move the fields directly to the usernode? It would be easier for theming, etc..
Would like to know about your thoughts about this.

I am also using loggintobogan, whith the option to login directly (without email confirmation), the way this works is that the user gets logged in with a special role (previously chosen by admin). After confirmation of the email, the user gets promoted to the authenticated user role. My question is when is the usernode created? could the "unverified user" modify usernode if he has permissions? I´ve tried it, but i think the usernode wasnt created, not sure if the error is adding cck fields to usernode, or the issue of no usernode being created. ill try with your latest dev version and see.
Thanks.

Comments

jpetso’s picture

jpetso commented

> My question is when is the usernode created?
It's being created when a user is created, that is, on registering or with an admin adding a new user from the user administration panel.

> could the "unverified user" modify usernode if he has permissions?
yes, if he can edit own nodes then he can potentially modify the usernode. in practice, you won't make it far by going this way because the usernode is just an empty node without even a "body" field. usernodes are designed to be extended with code, for example, usernode_view adds a link for each "child node" of the usernode content type (which is defined with the nodefamily module).

> I´ve tried it, but i think the usernode wasnt created, not sure if the error is adding cck fields to usernode,
> or the issue of no usernode being created. ill try with your latest dev version and see.
The current 5.x-dev version has a bug where usernodes for newly registering users are only created with uid 0 (Anonymous) as owner. A fix is available here, but it's not yet applied.

billmurphy’s picture

billmurphy commented

I tried the fix, it´s the first patch I apply!! worked fine. now I use the latest dev module. I still have the doubt of why not adding cck fields to the usernode directly.
> in practice, you won't make it far by going this way because the usernode is just an empty node without even a "body" field. usernodes are designed to be extended with code
CCK permits adding fields to the usernode, at least last time i tried. Is this a bug?
Is it reasonable to add some basic user profile information to the usernode with cck? I guess it could be a bit more eficient (not sure really).
Thanks for your time and help.

fago’s picture

fago
Primary language German
Location Vienna
commented

Yep, it makes sense as long as it fits to your case. ;)
However keep in mind, that these nodes are autogenerated, so putting required fields into it will result in some confusing issues: e.g. if an admin edits such an usernode he has to fill out the required fields for the user.

billmurphy’s picture

billmurphy commented
Status: Active » Closed (fixed)

OK, i've tried both approaches, and I guess I'll create a new node to store profiles, as it is originally intended :D
I was thinking and if this module was ever going into core, I guess it would be a good idea to keep the information (user, password) in the usernode.. but i'm still far away from understanding the core... :)
Thanks for your support!