Dara

Hi jaromeh (@jaromeh),

Here are two simple workarounds:

<style>
.bpfwe-range-slider .field-wrapper .before {
    right: 5px;
    left: auto;
}

.bpfwe-slider-values .before {
    display: none;
}

.bpfwe-slider-value-min::after,
.bpfwe-slider-value-max::after {
    content: "$";
}
</style>

<script>
jQuery(document).ready(function($) {
    $('.bpfwe-slider-track').each(function() {
        const $track   = $(this);
        const $wrapper = $track.prev('.bpfwe-range-slider');

        if (!$wrapper.length) return;   // Skip if HTML differs.

        // Read min/max from the range handles first.
        let minStr = ($track.find('.bpfwe-slider-min').attr('min') ||
                      $wrapper.attr('data-min') || '0').toString().replace(',', '.');

        let maxStr = ($track.find('.bpfwe-slider-max').attr('max') ||
                      $wrapper.attr('data-max') || '0').toString().replace(',', '.');

        const min = parseFloat(minStr);
        const max = parseFloat(maxStr);

        if (isNaN(min) || isNaN(max)) return;

        // Determine highest decimal precision.
        let decimals = 0;
        const minDecimalPart = minStr.split('.')[1];
        const maxDecimalPart = maxStr.split('.')[1];

        if (minDecimalPart) decimals = Math.max(decimals, minDecimalPart.length);
        if (maxDecimalPart) decimals = Math.max(decimals, maxDecimalPart.length);

        // Calculate precise step (e.g. 3.56 → 0.01; 0.0737 → 0.0001).
        const step = (decimals > 0) ? Math.pow(10, -decimals) : 1;

        // Apply step only to the relevant inputs (number fields + range handles).
        $wrapper.find('input[step]').add($track.find('input[step]')).each(function() {
            this.step = step;
        });
    });
});
</script>

The CSS moves the currency symbol to the right and the JS adjusts the slider and field step based on the detected decimal from the values. This should prevents unwanted rounding side effects.

Hi jaromeh (@jaromeh),

Just a quick update, I’ve pushed a new version that fixes the issue with search results not staying within the query context when filters are applied. It should now work correctly out of the box when using the “Dynamic Archive Filtering” option on search results page.

I also added a numeric range slider, that can be enabled with a toggle, when you choose a numeric range.

Feel free to update and give it a try.

Regards,
Dara

Hi jaromeh (@jaromeh),

Thanks for sharing this, that’s a valid workaround. In the meantime I was able to identify the problem and have implemented a fix so the search context is now maintained automatically when Dynamic Archive Filtering is enabled on search results pages.

Regarding your note about the price filter, there isn’t a range slider yet, but it’s something I would consider adding in a future update alongside this fix.

There isn’t a paid version, but I do plan to release an extended version more focused on WooCommerce. That would include better handling of product-specific queries such as price, stock status, and other meta-based filtering.

Thanks again for the feedback

Dara

Hi AlfonsoH (@alfonsoh)

You’re are right, the hierarchy options is also only available for filter types that support them, like checkboxes. Glad you got it working!

Please let me know if there is anything else.

Regards,
Dara

Hi nicorsm93 (@nicorsm93),

Thanks again for the detailed report. I ran additional tests and was able to reproduce the issue on my side. I’ll be working on a fix to improve support for these style properties.

In the meantime, if you’d like, I can suggest a few workarounds depending on your setup.

Regards,
Dara

Hi nicorsm93 (@nicorsm93),

Thanks for the detailed report. It highlights something I never explicitly documented. Background images must be set using the plugin’s dynamic image tag to render correctly with the filter. The dynamic tag is “Image Custom Field” under the Custom Dynamic Tag and it works with both regular meta and ACF fields and is also compatible with galleries. It uses its own class to apply the background image when the loop is rendering. The system was designed to work standalone without Elementor Pro. This should resolve the issue you are observing.

Please let me know if there is anything else.

Regards,
Dara

Hi fulloken,

Thanks for the update, I’m glad to hear the search bar is working for your needs.

I have just tested the search bar together with the loop grid pagination on my side and the pagination URL are generated correctly, including the page slug. When the redirect option is enabled on the search bar, the pagination also works normally.

It is possible that something specific to the page setup or permalink structure is affecting the pagination links.

Could you please share the URL of the page where this happens so I can take a closer look? If the page is not public, a temporary preview link would also work.

Regards,
Dara

Hi Fanchon (@adverti),

Yes, this is possible, but it requires combining two things and a small custom implementation.

BPFWE filters can be triggered directly through a URL. For example:

https://yourwebsite.com/?results=filter-8ff8b79&category=61%2C17%2C43

In this URL:

* ?results is added to the URL to trigger the script
* filter-8ff8b79 is the filter ID (it can be found at the bottom of the widget settings under “Additional Options”)
* category=61,17,43 represents the selected taxonomy terms

After adding ?results=filter-XXXXXXX, interacting with the filter will reveal the different URL arguments.

The BPFWE Search Bar also includes a “Redirect After Submission” option, but this only redirects with the post type and does not pass the filter parameters.

If you want a filter bar on the homepage and results on another page, the usual approach is:
1. Create a simple HTML form with a search field on the homepage
2. Build a URL containing the selected filter parameters
3. Redirect the visitor to the results page using that URL

When the results page loads, BPFWE will read the parameters and apply the filter automatically.

This isn’t part of the current built-in features, but it can be implemented with a small script or custom form. This type of implementation requires custom development and falls outside the scope of plugin support, however tools such as ChatGPT or Claude can usually assist with generating the form and redirect script once you know the required URL structure.

Let me know if you have any other questions.

Regards,
Dara