I think I need to use usernode...but I am having trouble grasping it...

My goal is to allow users to use the core upload file module to attach files to their user profile.

I installed usernode and made sure the usernode content type allowed file attachments....but nothing seemed to get added to the user edit page (http://mysite.com/user/[uid]/edit) - should it have?

I also see the user's user node page (at: /usernode/[uid]) but there are no options to do anything on that page except for get forwarded to the user's profile page.

I also tried adding an image cck field to the usernode content type but that didn't allow me to add an image to the user's profile.

What am I missing here? usernode doesn't seem to do anything...

I even tried creating a new user thinking it didn't do anything for existing users but that did nothing either.

Comments

jmlavarenne’s picture

jmlavarenne commented

The usernode does not do anything. It is used as a reference. Normally usernode takes over all links to a user page. So instead of http://mysite.com/user/[uid]/edit you will get there by http://mysite.com/node/[nid] where nid is the node id for the usernode associated with the user. I don't remember if this happens automatically or if you have to make it do so, but normally when if you point your mouse over a user name, like where the author name is displayed as a link, you have a link to the usernode (node/[nid]) instead of the user/[uid].

What you can do is create another kind of node, for example profile_files, and adding all the cck fields you need and file upload settings you need.

The simplest way to do this might be to use the nodeprofile module and add the necessary fields to that node type.

After that you can create a node-usernode template file and use the functions found in the nodefamily readme text file to call your node type and edit it as you wish.

This will let your users edit their profile node from their account page if you set it up accordingly in the nodeprofile content type setup page.

You can also make other node types part of your profile arrangement. You need to make parent/child relationships using the nodefamily module between the node types you want associated with profiles. You should restrict the population of those node types to 1 per user.

I recommand taking a look at the readme files for all three modules - nodefamily, usernode, nodeprofile. They very informative.

mdowsett’s picture

mdowsett commented
Status: Active » Closed (fixed)