-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
children_only being set to true doesn't honor base_url but only gets tags of children of page TWIG code is in #38
Comments
To be clear, if I do NOT put in ... Simple IncludeThe plugin provides a Twig template that you need to include in your theme. Something like:
Where Child-only IncludeYou can also include pass an optional parameter that will show taxonomy for child-pages only:
... So the first bolded line seems to indicate that doing so--displaying all tags throughout the site--IS the intended behavior if you do NOT specify/set |
I have the exact same problem - it seems I can't meaningfully combine the two factors, right? Following scenario:
Desired outcome:
Any suggestions on how to set this up? |
Hi @flow7
And in your taxonomylist.html.twig this:
|
It is very possible I misunderstand the intention and that this is by design, but it seems like the
children_only
setting is not taking into account thebase_url
setting. Instead, it is only taking tags from the children pages of the page where this code is being loaded.As an example, I am using Grav with Gantry5's Helium theme and was trying to create a sidebar on both the blog_list as well as individual blog_item pages that would list the popular tags from all the blog posts (but only those pages and not all the pages on the site). So I thought that by using code such as the following, this would be achieved:
Now this works perfectly on the blog_list page that is at
/blog
. But the moment you load any blog_item pages, this code loads up an empty list. This makes sense if it is assuming children of the blog_item page, but that seems contrary to the idea. I would think the 2 parameters define what pages the plugin checks for tags. But again, it could be I misunderstand this.Is this the actual design? And if so, is there a way to achieve what I am trying to do? Because I don't see a way to do so.
The text was updated successfully, but these errors were encountered: