Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-settings.php on line 186

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/backpress/functions.wp-object-cache.php on line 108

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/backpress/pomo/mo.php on line 171

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/functions.bb-l10n.php on line 484

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/backpress/class.wp-taxonomy.php on line 581Bring navigation files back (Options theme) « Community

The community forums are currently being phased out. At the end of February or early March 2012, you will no longer be able to post here. This is because the entire site is being restructured. Please use the main forums for discussions.

Bring navigation files back (Options theme)

I think one of the most confusing things about version 1.3 of the Options theme has been the missing navigation files. Of course, I've had a sticky post up about this on the Options theme forum to help users adjust.

There was one good reason for this major change — to allow for more change in the future. In the next version, I had planned to let users pick and choose which categories/pages they wanted to appear in their navigation menus from the Options Settings page.

The alternate route, which would require you to edit the files manually, is bringing back the old main-nav.php and sub-nav.php. This would entirely halt progress in this area, but maybe some things shouldn't be developed any further.

My proposal is to bring back the navigation files, so users can edit them manually. Rate up if you'd like to see this happen in the next version and would rather manually edit the files.

In the next version, I had planned to let users pick and choose which categories/pages they wanted to appear in their navigation menus from the Options Settings page.

Justin, editing main-nav.php is one of the most support questions users ask in the helping forums. So, I think its nice to let the users choose the categories/pages they wanted to appear in their navigation menus from the Settings page. So, non coder users will not get mad between the lines...

I concur with JMehmett. Simplification is good - if it's good for the users, it should also be good for you. This, of course, subject that development is "easier" or more robust in the future. I think, as long as we can tweak the css all we want then we are free to personalize. Development nd customization should be done be you based on your roadmap as well as the users "requirements".

The more one can manage through the admin panel the better - at least that's how I feel - right or wrong, I don't know...

I started to write that I'd like to see main-nav come back but after thinking it over further, I don't think that's the right way to go. A far simpler solution is to sticky a definitive post on doing this through functions.php. In either case, a file has to be edited so why break from the philosophy of child themes just as we're trying to embrace it?

What is leading to confusion is inconsistency among several threads on the subject. Some examples include threads with working code that doesn't include dynamic highlighting for manually entered pages such as Home while other threads contain code that don't seem to work at all.