Forums / Setup & design / parent_node_id - Where does it come from?

parent_node_id - Where does it come from?

Next topic

Author	Message
RW Wood	Monday 08 September 2003 7:34:42 am As I'm learning to understand the templating system, I see that the menus on the demo site are generated by fetching content that has parent_node_id set to a number, ie 17 for the news site, 19 for the book corner, etc. However, I don't know how a template designer is supposed to know those numbers without going into the database and tracking them down. Is there some part of the admin database that I'm missing that would show these node numbers? Additionally, I still don't get the idea of nodes as opposed to a folder structure with child folders and files, etc. Thanks. RWW
Bjørn Kaarstein	Monday 08 September 2003 7:49:36 am You can find this out in the admin interface. If you create an object (article, folder etc), then you'll have a link to your new object. In the status line you can see i.e. /content/view/full/19 where 19 will be your node number. You can also get your nodenumber in the templates with {$node.node_id} Ez has a tree structure, with node 2 as the top node. Basically, every object can have children objects of different types. Regards Bjørn
Alex Jones	Monday 08 September 2003 7:50:44 am -- Looks like Bjørn beat me to hitting the 'Post' button. :) -- You don't have to go into the database. If you look at the content section of the admin area and click on one of the links such as "Book Corner" you will be taken to that node. If you look at the URL in your browser's address bar you will see a number at the end of it which is your node id. Every "page" or "folder" has its own node id; for example, the main node id for the root folder is most likely '2'. I think of nodes as being far more flexible than a folder structure. Folders in and of themselves are rather useless in this system as any item can act as a container for children. So you can set up a press release that is a child of another press release if you wish. It can be both confusing and powerful. ;) Hope this helps, Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Hans Melis	Monday 08 September 2003 7:54:30 am EDIT: I'm even slower ;) You can see the node id's in the admin interface. Hover the mouse cursor over an object's name, and the url for that object will appear in the status bar. The node id is after /content/view/full/ However, when click the "Edit" picture, it won't show the node id in the address bar, but the object id. Nodes serve as a container for objects. Each node has some attributes, and an object enclosed in it. In the most simple structure, you will indeed only have folders that create the structure. But with the node system, you can put anything anywhere in the content tree. With the folder system, you'd be restricted to placing content as a child of a folder. You can simulate the folder system with the roles though. Content; Create; ParentClass(Folder) as permission should do the trick. -- Hans Hans http://blog.hansmelis.be