why doesn't the nav bar show up in new pages?
Permalink
I thought I had this sorted. I make a new page then in the header bar I add new content and select the auto nav. My nav bar is now not implementing the style sheets that are working in my home page, the txt is larger and missing the background images.
Sorry but I'm designing on local host so I can't so you. I just want to know why is C5 designed so that we have to use auto nav? Can I just dump auto nav and use the traditional php header include for my nav. I like C5 and want to use it for all my web projects but hickups like this are really time consuming.
Sorry but I'm designing on local host so I can't so you. I just want to know why is C5 designed so that we have to use auto nav? Can I just dump auto nav and use the traditional php header include for my nav. I like C5 and want to use it for all my web projects but hickups like this are really time consuming.
to have it show up in new pages, it needs to be included in the page template you're using. Take a look at header.php & default.php for any of the core themes and you'll see how it works.
The autonav block is one of the awesome features of concrete 5, so no point in dumping it, you need to read the documentation and how-to's on autonav and only then you shall realize its true potential.
To have the nav bar to show up in new pages, you should add the nav bar to the Page type defaults .
You can check this video tutorial to understand the concept.
http://vimeo.com/3023508
To have the nav bar to show up in new pages, you should add the nav bar to the Page type defaults .
You can check this video tutorial to understand the concept.
http://vimeo.com/3023508
kappi,
two things,
1st - if you use Firebug you can take a look at the code on the active web page and see what's causing the hick-up.
2nd - the auotnav auotmatically outputs code including a <ul> tag. In the past, any style issues I had were because I had left the <ul> tag in my template and then a second one was being outputted by C5. This caused funky styling.
But I agree with the other posters - you want to keep the autnav. If not, anytime you add a page or change it's name you will have to manually change instead of just letting the CMS do it for you.
two things,
1st - if you use Firebug you can take a look at the code on the active web page and see what's causing the hick-up.
2nd - the auotnav auotmatically outputs code including a <ul> tag. In the past, any style issues I had were because I had left the <ul> tag in my template and then a second one was being outputted by C5. This caused funky styling.
But I agree with the other posters - you want to keep the autnav. If not, anytime you add a page or change it's name you will have to manually change instead of just letting the CMS do it for you.
