Hi @julzee
This is just a message from the widget itself, which is incorrect and will be fixed. Once you apply the Filter Set on that page, this message will be replaced with the filters.
However, please note that the Free version does not work with custom queries.
Best regards,
Victor
Thread Starter
julzee
(@julzee)
I published the page and it showed the same error. I disabled few plugins that could conflict. However, this did not solve the problem. The error message still appears on the frontend of the page. https://prnt.sc/uZEHEJ6oDsK8
What should we do to fix this?
@julzee Can you please update to the latest 1.9.5 version of the plugin and check it again?
Additionally, please send us the link to the exact page where this issue is occurring so we can investigate it.
Best regards,
Victor
Thread Starter
julzee
(@julzee)
Yes, we use latest version 1.9.5. Here is the link Elementor #29022 |
So, this is a singular page, meaning it is a static WordPress page (not a post, archive, category, tag, search, or WooCommerce page). The page is built with Elementor and uses Essential Addons for Elementor to display the posts on the page.
From the setup itself, we can already tell that this approach will not work, as it relies on a custom query. It is not the WordPress main query or the default Gutenberg Query Loop, such as the one used by the WordPress Twenty Twenty-Five theme.
We tested this on our end:
We were unable to reproduce the issue you reported. However, although we can display the filter on the page, we cannot actually filter the posts. Instead, the following message would be shown: https://prnt.sc/Suk-dDM3sbP0
This is expected behavior because content displayed on singular pages or archive pages via custom queries is not filterable with the free version. Filtering custom queries requires the Pro version, as the free version only supports filtering the WordPress main query and supported default Gutenberg query loop.
Best regards,
Victor
