We are a developers group that are very much interested in using nodes for profiles. There is a module, and some other code already, but that needs polishing.
Especially for bigger and more complex communities, people need features such as finer grained permissions on profiles, categorising of users, or simply search in profiles. Nodes offer all that. We tie them together.
nodeprofile progress & views fusion
I've got a views integration for my nodeprofile modules working. This also works for general nodes, not only for nodeprofiles.
By doing the nodefamily views integration I ended in writing the module views_fusion:
With this module its possible to build views which display information of several nodes in one view - useful for tabular views.
This is achieved by defining multiple views, one for each node. Then the views fusion module is used to melt these views to a big one which contains all the information.
More information on this module
This module works great together with the nodefamily module, so it's possible to use nodefamily relations for joining the views/nodes. However I've written the module in a general way so that it's possible for other node relation modules to use it the same way.
Of course testers and feedback are welcome.. :)
Read morenodeprofile modules - first code available
As I've already posted, I'm working on nodeprofiles as summer of code project - project page. Now I've some first code you might be interested to test.
I'll try to give you a short overview of the modules I built:
usernode.module - Automatically creation of usernodes
nodefamily.module - Builds nodefamilies based on content types and author information
nodeprofile.module - Marks content types as profiles
check the readme or my site for more detailed information.
Read more
User registration and profiles
Does someone have any thoughts about multiple user registration paths (imagine fans and bands for a music site) that are linked to specific roles that are in turn linked to profiles?
The idea is that admin defines certain roles for users on the site, each role has a separate registration path and can have profile fields that are separate for each role and can be customised by the admin. Or, admin could define a set of common profile fields for all the roles (that would then appear in the respective registration paths) and additionally specify custom profile fields for each role.
Add to this the following and I think we would have a really useful profile module:
Read moregoogle summer of code project: nodeprofile
As you may have already noticed, I'm working on a soc project, which is quite related to this topic:
Node Profile Module and CCK
The difference is, that I'll concentrate on using it with the CCK. However, I'll write code as much independend of the CCK as easily possible, so that my work might be with a custom built node type, too.
I've posted an implementation proposal here. Please post your comments and or suggestions - let me know what you think of it.
-fago
Read more
Profile nodes using existing modules
I've created a method for creating moderated profile nodes using the workflow, CCK, and action modules. It is still a work in progress, but it works.
http://www.techsanctuary.com/node/72
Read more
What should this module accomplish?
I got to thinking that we are maybe putting the cart before the horse and need to clarify the goals of this project. I see several, I'm sure others will see them differently or have completely different goals. Here are mine:
-
I want to be able to designate a specific content type as equivalent to a user record. There should only be one type that has this status so there is no question about which content type is the 'primary' user profile.
-
I want to be able to designate additional content types as types that provide additional user information, similar to the role of the profile module now. There could be several of these types for any one user record.
Address info in profiles
This is a continuation of a discussion at http://drupal.org/node/61902. Here's the discussion so far:
17 submitted by sym on May 16, 2006 - 08:25
I don't want to pull this too far off topic, but has anyone thought about using the ecommerce address module to handle profile addresses?
See http://drupal.org/node/63340 for more info.
18 submitted by Bèr Kessels on May 16, 2006 - 09:17
address (used to?) have states hardcoded. And that is a non option for The Rest Of The World [1]
Last time I looked address from ecommerce was long due an overhaul. With all due respect to the develpers that is! Somewhere, long ago, it scratched an itch, but it should have been updated long since. And yes, I am to blame for not doing that update just as much!
Read moreHow/Where to View & Edit node profiles
I thought I'd start a few thread about various issues that need to be thought through, along with my own observations about them.
First, how and where to view and/or edit the nodes?
My vote right now is that both should be in the user profile. My early sandbox efforts treated each node-profile content type as a user category, placed in its own tab on the user page. Not just on user/edit page, as with profiles now, but also on the user/view tab because the nodes can get much too large to just run them all together on a single view page.
It is possible to do this without much trouble (I have done it), so it is just a question of whether or not this is the desired behavior.
Read more
maintainer
We need one drupal.org project node and a CVS in contribs where we can place all this. For that we need a maintainer.
I volunteer to be that. But maybe others want to volunteer too. Please comment if this sounds like a fun idea to you! Please also comment whether or not you already have CVS access, because that is a critical factor.
Read moreinitial code
See attachements.
Stuff that is not yet properly worked out in this module, because it needs thought (instead of code) include:
where to edit the nodes (your profile)
where to view the nodes (where to render the profile)
how to limit the amount of nodes a user can post as profile in a nice way.
