Data Source Filtering Hierarchy
This is an open discussion with 2 replies, filed under General.
Search
i believe the last time i did something similar to this, i abstracted the template into a separate file that i imported into one page, let's call it beers
that accepted category/entry
as parameters, and another page with beers
as the parent called all
that only accepted entry
as as parameter.
this way it looks the same to the user, but it's technically 2 separate pages deferring to a shared template.
Thanks for the feedback, that seems like a good idea to try. I will try that route.
David
Create an account or sign in to comment.
Hello,
New to symphony so I am still working out how it puts things together. I had everything figured out for my current project, but have a new requirement that I am not sure quite how to address.
I have this kind of set up working already: /section /section/category /section/category/entry
and the page is getting cat/entry if present to know what to show based on filter in data source.
This seemed fine only now they want a 'view all' option, but maintain same type of url string. Only now, instead of 'category', it will be 'all-entries'. I was wondering what is the best way to work this feature into what I have.
I have considered:
Should I be trying something one of these ways for should I be taking a different path?
Thanks,
davlun