Observing unexpected UI change when presenting filtered results
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from fedhillphoto on October 15, 2025, 23:00Hello,
I have a filter set up on my main shop page here. The tag is inserted into the page via shortcode: [woof_front_builder name="Default"]. Each tag archive page has a second, different filter. Example here. The tag is inserted into the tag archive page via shortcode: [woof_front_builder name="Product Tag Archive"]. From a tag archive page, when I input a word, click Filter, I expect HUSKY to present the "Product Tag Archive" filter UI near the top, and the breadcrumbs just below the navigation menu to display Home>Fine Art Photography Gallery>Products tagged “<tag>”. Instead, I'm observing HUSKY presenting the "Default" filter UI, and the breadcrumbs just below the navigation menu disappear. What is causing this to happen?
TIA,
Carl
Hello,
I have a filter set up on my main shop page here. The tag is inserted into the page via shortcode: [woof_front_builder name="Default"]. Each tag archive page has a second, different filter. Example here. The tag is inserted into the tag archive page via shortcode: [woof_front_builder name="Product Tag Archive"]. From a tag archive page, when I input a word, click Filter, I expect HUSKY to present the"Product Tag Archive" filter UI near the top, and the breadcrumbs just below the navigation menu to display Home>Fine Art Photography Gallery>Products tagged “<tag>”. Instead, I'm observing HUSKY presenting the"Default" filter UI, and the breadcrumbs just below the navigation menu disappear. What is causing this to happen?
TIA,
Carl

Quote from Alex Dovlatov on October 16, 2025, 12:22Hello Carl
Desribe me please how you inserted shortcodes, make please video. How exactly you placed second shortcode into page https://fedhillphoto.com/product-tag/color-image
If this is https://fedhillphoto.com/fine-art-photography-gallery your predefined shop page, this will be shown every where where search is going if you not wrap it in some way programmatically. For example you can create your own custom shortcode https://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/ and man ipulte by that your shortcodes dependign of what is filtering
Hello Carl
Desribe me please how you inserted shortcodes, make please video. How exactly you placed second shortcode into page https://fedhillphoto.com/product-tag/color-image
If this is https://fedhillphoto.com/fine-art-photography-gallery your predefined shop page, this will be shown every where where search is going if you not wrap it in some way programmatically. For example you can create your own custom shortcode https://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/ and man ipulte by that your shortcodes dependign of what is filtering
Quote from fedhillphoto on October 16, 2025, 15:21Hello,
I placed the shortcode into the tag archive pages using functions.php. Here's the code:
/** if the page is a product tag archive page, echo the generic tag description text just below tag name **/ add_action( 'woocommerce_archive_description', 'bbloomer_loop_tag' ); function bbloomer_loop_tag() { if ( is_product_tag() ) { echo '<h4><span style="color: #008000;"><strong>Free shipping on orders over $100</strong></span></h4><p>For help, <a href="/fine-art-print-products-faq">see the fine art photography FAQ</a>. <br />If more questions, <a href="/fine-art-photography-inquiry">make a fine art photography inquiry</a>.</p>'; echo do_shortcode('<div style="width: fit-content; margin: auto;"><span style="font-size: 14pt;"><strong style="color: red;">Troubleshooting filter, please don\'t use.</strong><br/><strong>Filter images: </strong><a href="/fine-art-photography-gallery-faq#search">(How to use)</a></span><br />[woof_front_builder name="Product Tag Archive"]</div>'); } }
Yes, https://fedhillphoto.com/fine-art-photography-gallery is my pre-defined shop page. Using the wordpress editor, I added this html to the page:
<h4><span style="color: #008000;"><strong>Free shipping on orders over $100</strong></span></h4> <p>For help, <a href="/fine-art-print-products-faq">see the fine art photography FAQ</a>. <br /> If more questions, <a href="/fine-art-photography-inquiry">make a fine art photography inquiry</a>.</p> <div style="width: fit-content; margin: auto;"><span style="font-size: 14pt;"><strong>Filter images: </strong><a href="/fine-art-photography-gallery-faq#search">(How to use)</a></span><br /> [woof_front_builder name="Default"]</div>
Hello,
I placed the shortcode into the tag archive pages using functions.php. Here's the code:
/** if the page is a product tag archive page, echo the generic tag description text just below tag name **/ add_action( 'woocommerce_archive_description', 'bbloomer_loop_tag' ); function bbloomer_loop_tag() { if ( is_product_tag() ) { echo '<h4><span style="color: #008000;"><strong>Free shipping on orders over $100</strong></span></h4><p>For help, <a href="/fine-art-print-products-faq">see the fine art photography FAQ</a>. <br />If more questions, <a href="/fine-art-photography-inquiry">make a fine art photography inquiry</a>.</p>'; echo do_shortcode('<div style="width: fit-content; margin: auto;"><span style="font-size: 14pt;"><strong style="color: red;">Troubleshooting filter, please don\'t use.</strong><br/><strong>Filter images: </strong><a href="/fine-art-photography-gallery-faq#search">(How to use)</a></span><br />[woof_front_builder name="Product Tag Archive"]</div>'); } }
Yes, https://fedhillphoto.com/fine-art-photography-gallery is my pre-defined shop page. Using the wordpress editor, I added this html to the page:
<h4><span style="color: #008000;"><strong>Free shipping on orders over $100</strong></span></h4> <p>For help, <a href="/fine-art-print-products-faq">see the fine art photography FAQ</a>. <br /> If more questions, <a href="/fine-art-photography-inquiry">make a fine art photography inquiry</a>.</p> <div style="width: fit-content; margin: auto;"><span style="font-size: 14pt;"><strong>Filter images: </strong><a href="/fine-art-photography-gallery-faq#search">(How to use)</a></span><br /> [woof_front_builder name="Default"]</div>

Quote from Alex Dovlatov on October 17, 2025, 17:00Hello Carl
I think I have understood the core of the question.
Even though both filter frms technically work, here is what happens: when a search request is made, only the main Shop page exists in the global scope. So, when HUSKY processes a URL with filtering parameters, it always refers to the Shop page context, regardless of whether the query originates from a tag archive or another product archive. Everything is handled together through the same base shop page.
Because of that, there is really no practical reason to place a second filter on the tag archive page - unless you want to display some additional information for users. Both filter forms behave the same way, so keeping only one (the shop filter) will work perfectly, and customers will still find everything they need using that single form.
If I am missing your specific use case, please explain the practical reason for having two separate filters - I'll think about how this can be worked around. But for now, what you are seeing is completely logical and expected behavior.
Hello Carl
I think I have understood the core of the question.
Even though both filter frms technically work, here is what happens: when a search request is made, only the main Shop page exists in the global scope. So, when HUSKY processes a URL with filtering parameters, it always refers to the Shop page context, regardless of whether the query originates from a tag archive or another product archive. Everything is handled together through the same base shop page.
Because of that, there is really no practical reason to place a second filter on the tag archive page - unless you want to display some additional information for users. Both filter forms behave the same way, so keeping only one (the shop filter) will work perfectly, and customers will still find everything they need using that single form.
If I am missing your specific use case, please explain the practical reason for having two separate filters - I'll think about how this can be worked around. But for now, what you are seeing is completely logical and expected behavior.
Quote from fedhillphoto on October 18, 2025, 22:51Hello,
What's the purpose of the woof_front_builder shortcode's name attribute, if not to differentiate between different, individually configurable instances of filtration UI?
Hello,
What's the purpose of the woof_front_builder shortcode's name attribute, if not to differentiate between different, individually configurable instances of filtration UI?