Dara

Hi Mei Yin (@mei-yin),

There is no native setting that directly keeps the Loop Grid completely hidden until the filter interaction happens.

However, this can easily be achieved using CSS. The filter widget already adds an active class when a selection is made, which you can use as the trigger to show the Loop Grid only after interaction.

So essentially, the grid remains hidden by default and is only revealed once the filter becomes active.

Your CSS would look like this:

.your-wrapper-selector {
    opacity: 0;
    visibility: hidden;
    pointer-events: none;
    transition: 0.2s ease;
}

.your-wrapper-selector.filter-active {
    opacity: 1;
    visibility: visible;
    pointer-events: auto;
}

The CSS class added by the filter after an interaction is .filter-active and .your-wrapper-selector would be the same as your post widget target.

Hope this help.

Regards,
Dara

Hi tommyd17 (@tommyd17),

Unfortunately, numeric custom fields currently do not support value formatting. To avoid confusion, this option will be hidden for numeric fields in the next update.

For the euro sign, it can be repositioned using the following CSS:

.field-wrapper .before {
    right: 5px;
    left: auto;
}

This will be properly supported in the next update, which I plan to release later this week.

Regarding the decimal separator, this is mostly controlled by the user’s browser and system locale. It cannot be enforced consistently unless the browser language is manually changed.

Let me know if the CSS workaround works for you.

Regards,
Dara

Hi artemiusgreat (@artemiusgreat),

I checked the page and also tried reproducing the issue on my own my end using the same query options from the widget. On my side, the “Product Visibility” filter works correctly and I can successfully include or exclude out of stock products.

The fact that the product appears with a “Read more” button confirms WC correctly identifies it as out of stock, so this makes it more likely that something else is affecting the final query results on the page, such as:

– A third-party plugin modifying WooCommerce queries
– The active theme altering product visibility/query behavior
– Another query setting in the widget overriding or conflicting with the visibility filter
– Custom code/snippets affecting pre_get_posts or WooCommerce product queries
– If the post widget has a Query ID (this would directly influence the end results)

A cache could also potentially cause this behavior, especially if the product stock status or widget query settings were changed recently.

I would recommend temporarily testing with:

– Only Elementor + Elementor Pro + WooCommerce active
– A default theme such as Storefront
– The same widget/query configuration on a new clean test page

This should help isolate whether the issue comes from a conflict or from a specific page/query configuration.

Regards,
Dara

Hi Natacha (@chickwithbob),

When using a comma-separated list of classes or ID, each query is executed separately. Each widget keeps its own configuration and will return its own number of posts independently.

If this is not what you are seeing, please check under the “Performance Settings” in your filter. The “number of posts” value should be set to -1 so the loop widget is using it’s own post per page setting, otherwise the number set on the filter widget will take over and decide the number of post to display for all widgets.

Hope this help. Let me know if this fix the issue.

Regards,
Dara

Hi artemiusgreat (@artemiusgreat),

Thanks for your great feedbacks, and also for taking the time to investigate this issue.

Glad to hear you found the cause and got it working with the correct meta key.

If anything else comes up, feel free to open a new thread and I’ll be happy to help.
Regards,

Dara

Hi Nicola,

This feature has already been implemented on my side. Boolean formatting is part of the upcoming 1.9.0 update, which also includes several other improvements and new features. I bundled it into a larger release rather than pushing it as a small standalone update.

If you need early access for testing or to move forward with one of your projects, feel free to reach out at [email protected], and I can share a build with the boolean feature enabled.

I am currently testing the different changes, but I do not have a precise ETA for the release yet.

Thank you for your patience.

Regards,
Dara

Hi dizajner (@dizajner),

The filter widget currently works only via AJAX after the initial loop is rendered, so it cannot modify the first PHP query. If you need pre-filtered results on page load, you would need to apply the filter at the Elementor query level (server-side via elementor/query hook) or using BPFWE Post widget query hook. Using $_GET, you should be able to make the custom query dynamic.

Hope this help,
Dara

Hi paradosseus (@paradosseus),

Thanks for the detailed report, that helps a lot.

You are correct, the problem is almost certainly caused by nonce expiration. Since you mentioned that excluding the page didn’t resolve it, it’s very likely that your server’s Object Cache (like Redis or Memcached) is holding onto the expired security data. In the meantime you could check if there is a setting to selectively disable object caching for that specific page or to turn it off.

I will be adding a function to the plugin to force-refresh the nonce on page load, regardless of cache state.

If you can share which caching plugin or hosting provider you are using, I will also try to replicate that specific environment for testing.

Regards,
Dara