Absolute URLS instead of relative ones

54 Posts

happyavocado Reply #11, 17 years, 10 months ago

Yes, I have been using the http:// bit....

I still don’t seem to be getting to the bottom of whether I can output absolute URLs with Wayfinder - does anyone know how I can achieve this? Or if it is even possible?

54 Posts

happyavocado Reply #12, 17 years, 10 months ago

I think I’ve found the answer in another post. Set the parameter &fullLink=`1` and it will output the whole url. I had a quick play around with it and seems to work.

741 Posts

ronaldlokers Reply #13, 17 years, 10 months ago

Quote from: happyavocado at Nov 03, 2008, 04:50 PM

I think I’ve found the answer in another post. Set the parameter &fullLink=`1` and it will output the whole url. I had a quick play around with it and seems to work.

Where did they get that from? That parameter is not on the original site: http://www.muddydogpaws.com/development/wayfinder/parameters.html !

I’m happy to see that you solved it

with regards,

Ronald Lokers
'Front-end developer' @ h2o Media

1,390 Posts

kongondo Reply #14, 17 years, 10 months ago

Quote from: MediaGuy at Nov 04, 2008, 02:09 AM

Quote from: happyavocado at Nov 03, 2008, 04:50 PM

I think I’ve found the answer in another post. Set the parameter &fullLink=`1` and it will output the whole url. I had a quick play around with it and seems to work.

Where did they get that from? That parameter is not on the original site: http://www.muddydogpaws.com/development/wayfinder/parameters.html !

&fullLink is in the wayfinder documentation that you can download from the wayfinder 2.0 page in the wiki wink

Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder

54 Posts

happyavocado Reply #15, 17 years, 10 months ago

Off topic...

Does anyone know how to instruct Wayfinder to output just the children of a container, and not the container/parent in a navigation?

i’ve posted this question on here already but have not had any answers, so thought i’d put it to you, Kongondo, as you have cleared up quite a few of my Wayfinder usses already!

Thank you in advance

1,390 Posts

kongondo Reply #16, 17 years, 10 months ago

Quote from: happyavocado at Nov 04, 2008, 03:39 AM

Off topic...

Does anyone know how to instruct Wayfinder to output just the children of a container, and not the container/parent in a navigation?

i’ve posted this question on here already but have not had any answers, so thought i’d put it to you, Kongondo, as you have cleared up quite a few of my Wayfinder usses already!

Thank you in advance :)

Yes....the thing to remember is that normally WayFinder only lists the descendants of the document specified in &startId. The key here is the word descendants. That’s why stating &startId=`0` will output all documents in the hierarchy - (there is no document with id=0) - i.e. the descendants of the root (=0). So, back to your question, assume the following document hierarchy case (the numbers in brackets are document ids - but u know that, of course wink

):

Grand/Parent (40)
-------Parent (15)
-------------Grand/Child 1 (16)
-------------Grand/Child 2 (22)
-------------Grand/Child 3 (14)
-------------Grand/Child 4 (24)

If you specify &startId=`15` Wayfinder will output a menu like so:

menu-------------grand/child 1 (16)
menu-------------grand/child 2 (22)
menu-------------grand/child 3 (14)
menu-------------grand/child 4 (24)

If you specify &startId=`40` Wayfinder will output a menu like so:

menu-------Parent (15)
   sub-menu-------------grand/child 1 (16)
   sub-menu-------------grand/child 2 (22)
   sub-menu-------------grand/child 3 (14)
   sub-menu-------------grand/child 4 (24)

Bottom line, the document specified in &startId is always left out of the output unless you use the parameter &displayStart, which is always used in concert with &startItemTpl and in this case the value of &startId must not be Zero

The above assumes you are talking about one parent document/container. If on the other hand you had multiple parents with children and you wanted to leave out all the parents, this wouldn’t work. In this case you would use the parameter &excludeDocs to exclude the parent documents.

Note that if you "untick" "show in menu" for the parent document that is the &startId, its descendants will still be output. However, if you "untick" "show in menu" for a parent document that is part of the menu (i.e. not the &startId), its descendant documents, i.e. the children, will also not be shown in the menu.

As usual, there’s probably another way of achieving these things....if there is, it will be pointed out here or somewhere else wink

Sorry for the longish post when a simple answer would have been enough. Just though I would make things clear, especially for the next person that comes along... wink

Hope this helps...all the above tested in modx 0.9.6.2

/k

Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder

54 Posts

happyavocado Reply #17, 17 years, 10 months ago

Hi Kongondo,

Thanks for the in-depth reply. I got all of that to work, but then ran into a stumbling block.

Here is my wayfinder call:
[[Wayfinder? &startId=`15` &level=`2` &excludeDocs &fullLink=`1` &outerTpl=`outer` &innerTpl=`inner` &rowTpl=`row` &outerClass=`subnavig`]]

15 is a parent, which means that the children of only this parent are outputted in my menu. I want to know if there is something I can add to the &startID bit to instruct wayfinder to output all of the children of a container, but only from the container that the current document is from. So, for the following example below, on pages 16, 22, 14, & 24 the navigation outputted would show only these pages and not those for Parent (16), and for pages 17, 23,15, & 25 the navigation will show only these pages, and not the ones in the parent (15).

-------Parent (15)
-------------Grand/Child 1 (16)
-------------Grand/Child 2 (22)
-------------Grand/Child 3 (14)
-------------Grand/Child 4 (24)
-------Parent (16)
-------------Grand/Child 1 (17)
-------------Grand/Child 2 (23)
-------------Grand/Child 3 (15)
-------------Grand/Child 4 (25)

I could use two different templates for each of these and set the startID to 15 and 16 respectively, but am wondering if there is some way I can do it all in one template.

Does that all make sense?

Many thanks in advance!

1,390 Posts

kongondo Reply #18, 17 years, 10 months ago

Quote from: happyavocado at Nov 04, 2008, 08:21 AM

15 is a parent, which means that the children of only this parent are outputted in my menu. I want to know if there is something I can add to the &startID bit to instruct wayfinder to output all of the children of a container, but only from the container that the current document is from. So, for the following example below, on pages 16, 22, 14, & 24 the navigation outputted would show only these pages and not those for Parent (16), and for pages 17, 23,15, & 25 the navigation will show only these pages, and not the ones in the parent (15).

-------Parent (15)
-------------Grand/Child 1 (16)
-------------Grand/Child 2 (22)
-------------Grand/Child 3 (14)
-------------Grand/Child 4 (24)
-------Parent (16)
-------------Grand/Child 1 (17)
-------------Grand/Child 2 (23)
-------------Grand/Child 3 (15)
-------------Grand/Child 4 (25)

I could use two different templates for each of these and set the startID to 15 and 16 respectively, but am wondering if there is some way I can do it all in one template.

Does that all make sense?

Many thanks in advance!

I am not getting the relationships in the hierarchy since you have two documents with id 16 in your example. Could you post an image of your actual hierarchy here? or, in your example above, is 15 the parent of Parent (16)? meaning, is the below your structure?

-------Parent (15)
-------------Child 1 (16)
---------------------Grand/Child 1 (17)
---------------------Grand/Child 2 (23)
---------------------Grand/Child 3 (15)
---------------------Grand/Child 4 (25)
-------------Child 2 (22)
-------------Child 3 (14)
-------------Child 4 (24)

Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder

54 Posts

happyavocado Reply #19, 17 years, 10 months ago

Shoot, my mistake!

It should be:

-------Parent (15)
-------------Grand/Child 1 (12)
-------------Grand/Child 2 (22)
-------------Grand/Child 3 (14)
-------------Grand/Child 4 (24)
-------Parent (16)
-------------Grand/Child 1 (17)
-------------Grand/Child 2 (23)
-------------Grand/Child 3 (15)
-------------Grand/Child 4 (25)

1,390 Posts

kongondo Reply #20, 17 years, 10 months ago

Quote from: happyavocado at Nov 04, 2008, 08:55 AM

Shoot, my mistake!

It should be:

-------Parent (15)
-------------Grand/Child 1 (12)
-------------Grand/Child 2 (22)
-------------Grand/Child 3 (14)
-------------Grand/Child 4 (24)
-------Parent (16)
-------------Grand/Child 1 (17)
-------------Grand/Child 2 (23)
-------------Grand/Child 3 (15)
-------------Grand/Child 4 (25)

ok, then this

15 is a parent, which means that the children of only this parent are outputted in my menu. I want to know if there is something I can add to the &startID bit to instruct wayfinder to output all of the children of a container, but only from the container that the current document is from. So, for the following example below, on pages 16, 22, 14, & 24 the navigation outputted would show only these pages and not those for Parent (16), and for pages 17, 23,15, & 25 the navigation will show only these pages, and not the ones in the parent (15).

needs editing too? or am I missing something? please explain...seems there’s cross-parenting here wink

Wayfinder Lessons: The (almost) Complete Guide to Creating Menus in MODx Using Wayfinder