So...an easy way to add a parent reference plus a straightforward way
to keep type creation links off the content/add page would pretty much
do it? <br>
<br>
Am I missing something? Because the new node identification method in
4.7 can be adjusted slightly to hide those links. A small change to the
array hook_node_info() returns (add an element to indicate visibility),
a new op for _node_names() (call it &quot;display create link&quot; or something)
and a small change to node_add() would do it. <br><br><div><span class="gmail_quote">On 11/18/05, <b class="gmail_sendername">Mark</b> &lt;<a href="mailto:mark@nullcraft.org">mark@nullcraft.org</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
&nbsp; One thing that was a problem the last time<br>I looked was how to go about restricting access to node/add/[type that<br>requires parent]/[nid of parent] without other things breaking.<br>Previous discussions led me to override the menu settings to disallow
<br>access to this path, but since the menu system does not prioritize it's<br>entries, you may find that your modification of the menu permissions<br>doesn't always work.&nbsp;&nbsp;The result is that the node/add page shows links
<br>to add content that is not allowed to exist without a parent. </blockquote></div><br>