cannot setup

Does the content type have cck fields? Those are required and are talked about in nodeprofile's documentation. That's why the tab in handshake setup is called "Choose CCK fields". Maybe list what the fields are that you have so I know what we're working with.

Also, after you turn a content type into a nodeprofile, you have to go back into the content type to edit it as there will be a new tab called "node profile". I don't recall off of the top of my head if any settings are required for this module to work or not. That's all I can think of at the moment.

Uh, this module is for sharing nodeprofiles, so that means profile style data, which isn't usually some kind of long text input as found in a body or even a title. And as title and body fields are the only standard content type fields, we don't care about them. Add to that the fact that body fields are not required (leave the body name blank and it won't show up) and the auto_nodetitle module allows you to hide the title and give the nodeprofile a meaningful and consistent name (I base mine on content type plus user id) and there is no compelling reason to share those fields. Plus, if you really want to share a textarea styled field like the body field, you can make a cck field instead.

I designed this module to work with several of my others for a project I'm doing. So although I've designed this for me and a specific use case, I also tried to make it somewhat generally applicable within reason. I am open to feature requests and patches to add or change functionality so long as my original design goals remain intact. The same can be said for my other modules. cck_address has received the most added value from user interaction. I have created a second project just to handle the user-contributed addons.

Anyway, I digress; let me ask you a question: It seems that people like yourself are having trouble doing what, in my mind, are simple things. I don't mean to insult you, I want to find out where the gap is in understanding as I may be assuming too much. My perception is that people should see what dependencies a module has and then begin understanding those before attempting to use the module that had the dependencies. And yet it seems this is not happening. Clearly I can't duplicate all documentation for those other modules as that would be a moving target due to their constant development. Any tutorials I might create which included steps for those modules would have a similar problem. Having re-read my README for this module, it seems adequate. So what misunderstandings and confusions did you have in the first place and how did they arise? CCK seems like a fairly obvious thing to me to have been missed, but others have asked similar questions (most notably over at my registration modification module). I can't just reply with a hearty RTFM every time "simple" questions come up. I am also somewhat annoyed that users that ask those questions don't offer any suggestions of how to avoid such issues once they figure things out. It would seem most beneficial if those kinds of users submitted revised READMEs or other documentation that they feel clears up the issues they had.

So sorry for the rant. Glad you got things working. I hope I answered your question well enough. Feel free to ask other questions or contribute answers that others can use.

That's very interesting, I haven't heard anyone put it that way before. I have hesitated to list as dependencies any modules that my dependencies depend on as they would technically be one level removed from mine and that could change without my knowledge. However, maybe I should add 'content' (CCK) to the list anyway.

Hi,
Is there any module for sharing the content created by a user. That is when i create a node, i want other user to handshake with me (or send a request) to view the content of that node.