tags:

views:

28

answers:

2

I don't know if I'm on the right track but I'm trying to let users of my web site create there own versions of pages on my web site. Basically I'd like to make our documentation used as a starting point where they just add details and make a new page for themselves in the process. I have a 'book' content type that I have changed with CCK and a 'client edits' content type that uses a nodereferencefromURL widget to link itself to the book node.

So simple version of what I'm saying is I have a link on my book pages that creates a node using client edits content type. I would like to put some fields on the client edits content type that take the values of some of the fields from the book page it is linked from.

I'm sure I'm missing something as I would have thought someone would have tried this before but I can't even find a hint on how to go about this.

All I really need is a point in the right direction if my current thinking is wrong. Current thinking is that I use a php script to get the default value for a field on the new node add screen that drags the value for a field from the book I'm linking from. I'm thinking this is the case because there is an option for default values for the field in cck manage fields that lets you put in a php value to return a default value for your field.

Am I on the right track or is there already a module or process that does what I'm talking about and I'm just too dumb to find it.

A: 

This sounds a little strange, are your client edits going to be a diff from the original node or just coppied data?

I would prehaps do it a more simple way, just have book nodes, and have different fields disaply depending on who edits it (enable the content_permissions module). That way you can use the node clone module to create the users copy.

You will need to make a module to contain your custom php code.

Jeremy French
I had brushed over node clone earlier in the week because I was more interested in coping fields rather than the whole node but I hadn't factored in permissions. I'll try that I see how it goes. Thank you.yes they are going to be different to the original as our program seems to get used in a thousand different ways depending on the client so they need to personalize our documentation for themselves and their staff.
Paul
Also the user must not be able to change original doc so if cloned does that mean they won't have permission to edit the new one as well as the field will be the same I guess? I'll try.
Paul
Permissions can be set so that user groups can only edit their own instance of something rather than every instance so you should be ok.
Jeremy French
This Answer is not quiet the way to go unfortunatly. Node clone is a good module and the permissions did work they way you pointed out so thanks for teaching me more about these before I point out why the fix didn't get me over the line.The problem is when you clone a node there is no way to reference the clone back to the origonal document. I need to do this.
Paul
My main page of documentation is tabbed into differnt parts. 1. A tab for the origonal document that my staff and I prepare for clients. This tab is viewed by my direct clients.2. A tab for the clone of the origonal that my clients prepare for thier staff. This tab will be filtered based on the client easily enough but without some kind of node refernce between the origonal node id and the clone how do I filter it so the right clone and only the right clone get's called. hope this makes sense. This is why I originlly tried nodereference. Thanks again for the original answer.
Paul
A: 
Paul

related questions