Symphony.

An extension would be quite easy to create I think. I started fiddling with a custom DS, my first, but then decided to ask around since, to me, it sounds like something that should be in the core. I'm surprised there are so few questions about it.

There's probably a couple of other ways to achieve this but I want to prevent loading lots of entries and filtering in XSL. I also thought having 2+ chained DS'es is overkill (plus: the Navigation DS Source does not allow for $ds-param -style chaining [why?])…

Anyway, when the {$parent-path} is available in the core it should be trivial to create a {$parent-page} param. But hey, I'm just a Symphony newbie :)

Anyway, when the {$parent-path} is available in the core it should be trivial to create a {$parent-page} param. But hey, I'm just a Symphony newbie

I believe I have overcome this issue in the past by doing some string manipulation on $parent-path in xPath.

Take a look at ends-with('/page/anotherpage','anotherpage) would result in true.

Lewis Thanks. And yes: that can probably be done (based on {$parent-path} and {$current-path}?) but seems like a lot of hassle. Besides: this would require us to still filter (potentially) a lot of entries in XSL, which is not ideal, right?

When I look at the/my problem from another angle I could say that the problem is not that I don't have access to a 'parent' but to 'children'. I can filter a Navigation DS on 'parent' which would give me all childpages. This is exactly what I need. However: I cannot use this info since the Navigation DS does not allow 'chaining' (parameter output). Why is this?

Looking at this from another angle maybe part of the trouble would be avoided if a Navigation DS would be able to output a $ds-navigation param…

Personally, I agree with you. I'm not sure there's any particular reason for the Navigation datasource not allowing parameter output, other than the fact that it was overlooked when originally conceived.

Yeah, I have tried looking into the DS and creating a custom DS (based on the Navigation DS) that would allow chaining but I'm not quite that far…

I have attached a mockup of what I am trying to achieve. Seems common to me :)

Then again: if no other Symphony users have run into this much I must be doing something wrong :)

Attachments:

sub-contentpages.jpg

Perhaps the URL Segments extension will fulfil your need?

Hi max, thanks, that might work. I've created a little custom DS that works fine though: http://symphony-cms.com/discuss/thread/65752/#position-9 but I'll take a look at the URL segments. although that would probably work too it seems a bit fragile since the parent page handle could be the same as another page, right?