Instead of forcing a single, hard-coded bio node of it's own type, this module would be far more flexible and powerful if an arbitrary existing node type, especially a flexinode could be used instead.

It would be even better if multiple types of node/flexinode could be assigned to user profiles, so for instance, a person could have more than one kind of personal bio entry.

As an example, there might be a "bio" for the standard bio, one for dating/friend-finder information, and one for someone's character/persona (for a gaming site).

This would also allow the existing search and node listing features be used to help people do searches for certain user information, such as to find other users with similar interests or certain specific criteria.

Comments

jjeff’s picture

jjeff commented
Status: Active » Closed (won't fix)

I think what you are really asking for is the ability to define extra fields on a bio. And I agree that this would be a great feature. I am hoping that CCK (content creation kit) will allow this type of feature. And while I'm willing to look at patches implementing this type of thing using flexinode, I'm more inclined to hold off until CCK is ready because that is the direction that flexinode is moving anyway.

As far as users being able to have multiple bios, it kind of kills the whole purpose of bio.module. The idea is that the user will be able to create 1 entry that will be linked to from their entries. Things would start to get dicey if a user could create more than one entry - which bio would their nodes link to?

Ultimately we're starting to blur the line between profiles and nodes. There has been talk about making profiles become nodes in later versions of Drupal. This module was meant to solve a few of these 1-user-to-1-content-item for use now. But what you are talking about really starts to replicate the profile functionality and is probably better discussed as an overhaul of profile.module rather than an extension to bio.module.