Page Tree Search Macro - Can You Set Default Filters?

[Scott Kesselring]

I am trying to add the Page Tree Search macro to a page. While the search box works fine, many of my pages have 5-15 attachments within them, and these attachments often include the Page name. For example, if I have a Page titled "Chicken Recipes," there are 10 attachments that are named "Chicken Recipes - Fig 1," "Chicken Recipes - Fig 2," etc.

This makes the Page Tree Search not ideal since every time I search, all of those attachments also appear. I know after I search, I can use the filters on the right to only view Pages. However, can I set the Page Tree Search to only search for "Pages" by default? I would only want to search by Pages and not by Blog Posts, Attachments, etc.

[Diego · Accepted solution]

Hello there, @Scott Kesselring ! I can see that setting up a default search parameter can be quite useful in your case. However, there is no setting for us to use as a default for the Page Tree Search Macro.

The macro acts more like a shortcut to the complete search rather than a separate search in itself. The filter that the macro applies is to reduce the search scope to the defined root page. The root page can be the current page where the macro has been placed or any other in the same space.

One thing you can do is use the Confluence Search Syntax to pin down results more quickly:

• [Confluence Cloud] Confluence Search Syntax

But, as you have noticed, there is no “default filter” setting for the Page Tree Search Macro.

I hope this clarifies things a bit for you, Scott!

[Scott Kesselring]

Hey Diego! Thank you for your answer! It does provide some insight.

I ended up working around the issue by using Labels and the "Livesearch" Macro. Since I only wanted Pages and not Attachments to appear in my search, I applied a Label of "Pages" to all my pages. Then I changed to the "Livesearch" Macro and restricted the search to only show results with the Label "Pages" and this worked.

Thank you for the clarification though!

[Diego]

Hello again, @Scott Kesselring ! Great to hear that you were able to reach your desired functionality within Confluence. Thank you very much for explaining how you worked around the situation.

Come share with the community again sometime in the future.