This is a continuation of the discussion in issue 84541 regarding porting this feature to the DRUPAL-4-7 branch.

CommentFileSizeAuthor
nodeprofile_3.patch8.33 KBdarren oh

Comments

fago’s picture

Title: Display nodeprofiles as profile categories » Display nodeprofiles as profile categories for 4.7.x

thanks for opening the new issue. I just want to point out that this issue is for 4.7.x by adding it to the title.

liquidcms’s picture

a couple things about the patch.

1. i dont think you included the couple mods i made to it to have only the tabs that go with your role listed as well as the uid fix that is required

and, more importantly:

2. i just noticed this now.. at first i thought the nodes were created even if they were not created during registration - i.e. registerprofile - which would have been very cool since you don't want to force the user to "create a node" simply to edit some of his user info. but i now i am not sure this gets done. This is what i have:

i have a user that did not have a "hobbies" node created as it was not part of the registration process (initially it was so i have some users for which this node had been created when they registered - these accounts work fine).

for users who didnt get the hobbies node when they registered i can see the "hobbies" tab listed under user/edit due to this patch... but a few things are odd about the form for this:

1. i use auto-nodetitle to hide the title field - it isn't working for this node for these users (but does for the others) - after a little digging i see it is because the node doesnt exist and therefore it has no $node->type and therefore auto_hidetitle doesn't work
2. i also, for more or less the same reason, was getting "file attachments" be allowed for this even though it is turned off for this type.. but it doesn't know the type.. so it puts the form_alter there.

so i tried to add text into the unlabeled, unhidden title field and do a save to see if this would at least create the node.. and this fails with a "data out of range" warning.. and the node does not get created.

not sure if this is a limitation with this patch - i suspect something that is missing in nodeprofile or that possibly i just missed in my setup..

Any ideas?? should nodeprofiles be auto-created even if they are not part of registerprofile? I guess this is awkward since i think it is possible to have numerous nodes of a nodeprofile type??? in which case who is to say there needs to be at least one.. although in my app and i suspect MOST cases this would be the case... AGAIN, looking at the profile module... you can have profile pages which are not presented during registration but also do not require the suer to create them to be able to fill them out.