nodeprofile

I'm happy to announce nodeprofile 5.x 1.1!

Thanks to the great subform element API module, which I wrote originally for pageroute, it was quite easy to implement some great new features for the node profile module, which make building simple node profiles a lot easier. So node profile 1.1 features

• configurable user edit categories integration - edit a simple nodeprofile like a core profile
• configurable node profile display integration on the user's (my account) page or - if used - also on the usernode
• configurable user registration integration
• easy integration of a nodeprofile in any theme

You can find the settings to this new features in the also new per content type node profile settings - just edit your node profile content type and click on the new "Node Profile" tab.

Read more about the new features on http://more.zites.net/nodeprofile_1-1

First off, wow - there's a lot of information, and a lot of tricky configuration here, but to some potentially great results. And congratulations on the documentation! I would never have gotten myself this far! :-) I'll describe ultimately what I want to do, what I've done, and where I'm stuck.

Is it better to user the usernode as the external display of a user's profile or is it better to use the profile page created via the content type? Right now I have the usernode established as the user's own profile page with edit links but I also want to display the same info to registered users.

Hi. I'm in the process of setting up a new drupal-based website for a community radio station in the UK.

I want to give each presenter (DJ in the station lingo) a profile page that shows a picture, has a voice clip (of them saying hello or something), and a bit of text about them.

The user description pages in drupal can show a picture, but I can't do a voice clip or body text.

I've installed nodeprofile, and I've read older posts here, on the drupal forum, and links, and I'm still rather confused.

Basically, what does nodeprofile actually do? When I mark a the content type as user profile, what changes?
When I click my user name at the top of a post, I still go to the old profile page, not the new content type, so I don't see any difference.

I'm following the readme for making a simple user profile, which is what I want:

• Create your content type you want to use for your profile, e.g. with the CCK.
  -- done that

Hello again :)

I´ve managed to create profiles nodes and attached them to several users on my demo installation. It was easier that I realize at the beggining (thank to your help guys!!). But this way, people have two profiles, and that´s pretty confusing, because they will have to edit both when they want to change, ie. their email or telephone number.
I know that thare´s a way to change the "original" profile link for the new profile_node, but what if I don´t want all users to be allowed to create their "new" node_profile?

Hi there!
I´ve been searching the forums for a while, and I´m sincerely lost about this issue.

I came to realize that there´s NO WAY to add taxonomy terms to the simple, yet easy, core module "profile".

So, I´ve installed the nodeprofile module. It needs the nodefamily to run, and it suggests you to install the usernode module.
I´ve done all that, and I´ve readed the readme files of all of them.

And yet, I´m clueless about how to replace the profile with all this confusing stuff. I´ve installed three modules already to replace one.

SoC is ending soon and a lot of code has been written. So I would appreciate if you could help testing my modules!

The modules I've built are:

• nodeprofile.module - Marks content types as profiles
• usernode.module - Automatically creation of usernodes
• nodefamily.module - Builds nodefamilies based on content types and author information
• views_fusion.module - Provides fusing of multiple views.
• pageroute.module - Allows the creation of userfriendly wizards

All this modules are compatible with drupal 4.7, so use a recent 4.7 install to test.
All modules except of the nodeprofile module have been built generally, so that they are useful for all nodes, not only for nodeprofiles!

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.. :)