Collect the node IDs the menus will use
The menu lists can be written in one go at launch.
Life cycle: Plan, example 17 of 35. Worked out on the Fit & Healthy site of Exponential 6.0.15+.
Contents
In the Layouts editor
- Each page in the administration shows
Node <id> · Object <id> · Remote ID.
In the content tree
- Write the node IDs into the plan per menu position; keep the remote IDs too, which stay the same when content is moved to another installation by package.
Which to choose
Node IDs are what MainMenuID[] needs; layout exports refer to content by remote ID and path as well.
Check
- Every planned menu entry has a node ID.
Related pages
- Find a node ID
- Plan examples, every page
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.