This is a wonderful wonderful module. It does exactly what I need, except...
I conduct online writing training, where my students are given a scenario and then write based on that scenario. So I need to be able to embed different "scenario" nodes, depending on the particular assignment. Hundreds of scenarios.
Node Reference URL does this, but the referenced node only displays on the saved target node. I need it to display on the edit form as well, so the writer can refer to it as he does his work.
You have demonstrated that a referenced node can be displayed as static text on an add/edit form. And I know that Node Reference (and Node Reference URL) can display the referenced title on the add/edit form. Can you give me any guidance on how to do what I want to do?
I am a beginner's beginner when it comes to code, but it seems like I need to make some kind of edit to one of my template files to get a referenced node to display on the add/edit form of a new node.
Please help.
Comments
Comment #1
m_i_c_h_a_e_l commentedA bit of clarification:
I think what I'm asking is, what does your module do to cause the body of a referenced node to appear on the add/edit form (which the basic Node Ref CCK field cannot do)?
Comment #2
mattyoung commentedCCK field has a widget part for editing/creating the node and formatters part for output. CCK field widget normally is some form element. Nodeincck's widget just display the content of a node. That's why in the node edit form, static text from another node is shown.
For what you need, use this module with token. In the nodeincck field config where you enter a node id, you can put a token instead. Let's say this token is
[writing-training-scenario].The second part is to create this "
[writing-training-scenario]" token to do the "finding the node to display base on the URL". This involve writing some code/module. Something like this:Let me know if you need help or something I need to fix in this module.
Comment #3
m_i_c_h_a_e_l commentedThanks for that really quick feedback. I fully understand the token part. Creating a token module, however, is way over my head... but I'm gonna dive in and give it a try.
A couple of questions:
Do you recommend using tokenSTARTER, since making user-generated tokens seems to be its specific purpose? Or should I try to build the module from scratch?
And second, will this actually behave like a souped up nodereference url? Meaning, the referenced node (drawn from an argument in the url) will display in both the target node edit form and in the final saved node?