Allow multiple nodes of a nodeprofile content type per user
wmostrey - August 21, 2007 - 11:08
| Project: | Node Profile |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
It would be great to be able to create multiple nodeprofile nodes of the same content type per user. For instance to have an "address" content type to allow users to enter multiple addresses. Currently the "Maximum population" field by nodefamily gets grayed out when enableing the nodeprofile option.
#1
for a profile it makes no sense to have more than one. However you could extend your nodeprofile with another content type "address" and create a nodefamily relation between them. Read the "extended nodeprofile" docs (handbook, READMEs of nodeprofile and nodefamily)
#2
Using this module for a couple of days now. I have a car site with one userprofile for the person's details and one for his cars and yes people have multiple cars. It would be great to have this feature. Besides, nodeprofile does allow profiled nodes without a limit of 1 per user so I think its a bit inconsitent not to display all nodes marked as nodeprofiles in eg the users profile. Now we're getting an arbitrary (first?) node while there are more.
Could you reconsider the won't fix status based on this example. I'd be happy to test but I'm not a great programmer.
Thanks,
Johan
#3
Nodeprofile doesn't allow more than one node per user.
>inconsitent not to display all nodes marked as nodeprofiles in eg the users profile. Now we're getting an arbitrary (first?) node while there are more.
This is not supported/allowed and this won't be changed.
#4
I'm trying to create this functionality using your suggested solution: nodereference.
I'm using addnode to create the node inline, but it looks like the form-values aren't populating the database. It seems that subform elements are somehow being bypassed via nodeprofile.
Here's the scenario: If I use addnode to inline-create a referenced node while *manually* (aka, node/add/x, not in the registration process) creating a nodeprofile-enabled node, it works just fine. However, if this is part of the registration process, then the inline-created node isn't properly linked in the nodereference.
My hunch is that maybe nodeprofile has a system weight that precedes other modules, such that populated subforms don't get into the database properly. I'm not really making sense to myself... but if you have any clues, as to whether this is an addnode or nodeprofile issue...
Edit: er.. your suggestion was nodefamily, wasn't it :)