User Side "Site Map" page creation

Permalink
I'm sorry if this is answered somewhere, already (I'm sure it must be, but I cannot find it -- all searches have been fruitless, and I find I'm banging my head against the wall!)

I'm trying to build a SIMPLE site-map for the FRONT end of a website (when I search for sitemap, all I get are references to the sitemap in the dashboard) -- looking to create a relatively standard looking one, with an outline layout, like this:

Home
-- About
-- Services
---- Service 1
---- Service 2
---- Service 3
-- Contact Us
-- Site Map

Now, I'm almost POSITIVE that (in the past) I've done this by simply placing in a page list block or an autonav, however, neither of these seems to be nested any longer -- they put all pages on the same level, like this:

Home
About
Services
Service 1
Service 2
Service 3
Contact Us
Site Map

I know I could try to build this myself, but I'm trying to save on time, and (like I said) I'm sure this has been done before -- just looking for a shortcut, I guess!

Thanks for any insight.

Darren

dihakz
 
pvernaglia replied on at Permalink Reply
pvernaglia
Set the sub page options in autonav to display all, I think you'll get what you want.
dihakz replied on at Permalink Reply
dihakz
That is exactly what I have! Take a look:
http://orgmylife.com/index.php?cID=64...
dihakz replied on at Permalink Reply
dihakz
No one has any idea?! Have I gone crazy?
LucasAnderson replied on at Permalink Best Answer Reply 1 Attachment
LucasAnderson
I'm not sure if this is what you're looking for, but here is a neat little auto-nav template that should show your sitemap in the treeview form like the actual Sitemap.

Also, I'm thinking your problem probably lies with CSS for bulleted list items, since that's how the pagelist/autonav display by default. You probably have something in there telling them to have no padding or margin.
LucasAnderson replied on at Permalink Reply
LucasAnderson
Yep, your reset.css is mucking things up for that list, since you don't define styles such as #nav li or #nav li a
dihakz replied on at Permalink Reply
dihakz
well, yes, that is true... however, the actual html looks like this:

<ul>
<li></li>
<li></li>
<li></li>
<li></li>
<li></li>
</ul>

If it WERE nesting the sublayers, shouldn't it look like this?

<ul>
<li></li>
<li>
<ul>
<li></li>
<li></li>
<li></li>
</ul>
</li>
<li></li>
</ul>

What I'm saying is that the markup is not even correct, even if I adjust my styles!
dihakz replied on at Permalink Reply
dihakz
that works great, thank you!
dihakz replied on at Permalink Reply
dihakz
yikes... I just realized... this is nice looking, and all... but that does not solve the issue of the autonav not embedding additional <ul> lists in there, to create the proper hierarchy. :(

Ideas, anyone?
LucasAnderson replied on at Permalink Reply 1 Attachment
LucasAnderson
Okay, here are some stupid questions, please do not be offended:

1. How are your pages setup in the actual Sitemap? Are they nested like you want or all on one level?

2. You're not using any custom templates here, are you? Very strange that the default view for the auto-nav block is not working as it should.

Can you compare your view.php in your concrete/blocks/autonav folder to the attached file and confirm it's the same?
dihakz replied on at Permalink Reply 1 Attachment
dihakz
No offense taken... afterall, you ARE taking the time out to help me, right? :-)

Yes, the page is the same. If it helps, here is a screen grab of my sitemap... it looks to ME that the other pages are nested under Home, does it not to you?

Is there another way to know the "level" a page is on?

Thanks!
Darren

http://cl.ly/1Y8R
LucasAnderson replied on at Permalink Reply
LucasAnderson
In this case, the auto-nav is behaving exactly as it should. You don't have any 'sub-level' pages under the first level, so it's not going to display them. (It adds Home on that first level as that's usually behavior for most navigation systems.)

In your sitemap, trying click on the Services page, then add a test page such as Service 1. I'm willing to bet you'll set it reflected correctly on your sitemap.