Hi Andrew - Thanks for the clarification and I see what you mean about complexity. In reality I suppose I would prefer to prevent my clients adding top-level items, so that the visual length of the main nav is constant, but I like that sub-pages all appear magically in sub-menus for dropdowns when I use wp_list_pages.
Given that, I guess I won't use the new nav feature at all unless I find a way of modifying it in functions.php. (Runs off to hunt for nav function calls & hooks on saving a page...) A graphic designer I sub-develop for prefers the simplicity we now have compared with menu building in his previous CMS, which was similar to the new WP nav. All best, A. On 2 Jun 2010, at 15:56, Andrew Nacin wrote: > On Wed, Jun 2, 2010 at 4:37 AM, Andrew Macaulay-Brook <[email protected]> > wrote: > >> When using menus, if I check "Automatically add new top-level pages", any >> new sub-pages I create are added to the menu too, but as top-level items >> rather then as children of their parent page. Is this by design or a >> genuine bug? > > > Sounds like I forgot about checking for an empty post_parent when coding > that. Will take care of it. > > In a way, it would be nice if hierarchical menus could be made automatically > > > We have thought about that but the UX implications were rather complex, thus > we stopped at the "auto-add" feature for now. We'd rather see how users and > developers use the menus in 3.0 and then enhance appropriately in a future > release. > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers Andrew Macaulay-Brook, BEng MBCS CITP, trading as theburo.net mailto:[email protected] • http://www.theburo.net/ _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
