Quote from klap3434 on August 29, 2026, 17:25

Üdv.
Olyan problémám lenne, hogy egyedi elementor oldalra tettem be a szűrőt a kezdőoldalra és egyedi oldalakat használok, meg jelenik a szűrő de viszont nem fut le újra tölt az oldal de nem hajtja végre a szűrést próbáltam már minden lehetőséget de hiába [woof_products limit="36" columns="4" paginate="true" is_ajax=0] ezt próbáltam utoljára elementor widget ben shortcod-al külön a szűrő [woof] magyarul használom a wordpresst azt hiszem ez az ajax:Szűrő automatikus beállítása ki van kapcsolva termékek jól vannak fent a webhsop ban nem tudom miért nem érzékeli a termékeket. Az a probléma, hogy nem a woocommerce nek a saját üzlet oldala van használva?

Quote from Alex Dev on August 31, 2026, 11:44

Hello

If we understood correctly: the filter form is placed on a custom Elementor page used as your front page, the form appears, the page reloads on submit, but the products are not filtered.

First, your shortcode has attributes that do not exist

You wrote:

[woof_products limit="36" columns="4" paginate="true" is_ajax=0]

limit and paginate belong to the WooCommerce [products] shortcode, not to ours. Our shortcode ignores them, so it currently runs on defaults. The correct attributes are per_page and columns:

[woof]
[woof_products per_page="36" columns="4" is_ajax="0"]

The full list our shortcode accepts is: columns, orderby, order, page, per_page, is_ajax, taxonomies, sid, behavior, custom_tpl, tpl_index, predict_ids_and_continue, get_args_only, shortcode, product_ids, post__in, display_on_search.

Note that is_ajax belongs to [woof_products], not to [woof]. The form itself takes its ajax mode from the plugin settings.

Please fix the shortcode first and test again.

Second, and this is probably the real cause

You are on an ordinary WordPress page, not on the WooCommerce shop page or a category archive. That matters. On a normal page the plugin deliberately does not force the product archive context onto the main query, because a page is not a product listing and interfering there would break other things.

So if your products are rendered by an Elementor widget rather than by our [woof_products] shortcode, that widget builds its own query and knows nothing about the filter. The filter writes its values into the address, the page reloads, and the grid returns the same products as before. That is exactly what you describe.

There are two ways out, pick the one that fits your layout.

Way one, use our shortcode for the products

Keep the corrected shortcodes above inside an Elementor shortcode widget. Our shortcode reads the filter values itself and returns the filtered products. The layout is then controlled by your theme's product template, not by Elementor.

Way two, keep the Elementor product grid and make it listen to the filter

If you want Elementor's own product widget for the design, add this to the functions.php of your child theme. It tells any product query on the page to use the ids the filter has selected:

 

//Make the Husky product filter work with page builder layouts
add_action('pre_get_posts', function ($query) {
	if (is_object($query) AND isset($query->query['post_type'])) {
		if ($query->query['post_type'] === 'product' /* AND is_page(1867) */) {
			if (isset($query->query['wc_query']) AND 'product_query' == $query->query['wc_query']) {
				return $query;
			}

			global $WOOF;
			if (is_object($WOOF) AND !empty(woof()->get_request_data())) {
				woof()->woof_products_ids_prediction(['per_page' => 99999]);
				$query->query_vars['post__in'] = $_REQUEST['woof_wp_query_ids'];
			}
		}
	}

	return $query;
});

 

The commented part, AND is_page(1867), is there on purpose. If you have several pages with product grids and only one of them should be filterable, uncomment it and put the id of that page in. Otherwise leave it as it is.

This is the documented approach for page builders and custom templates:

https://products-filter.com/make-page-builders-and-custom-template-filterable
https://products-filter.com/compatibility-with-elementor

One more thing to check while you are there

Open the plugin settings, Advanced tab. There is a field that limits the plugin to certain pages, one link or link mask per line, with a reverse switch next to it. If anything is written in it, empty it and save. A leftover mask lets the form render while the plugin stays switched off on that page, which produces the same symptom.

Tell us which of the two ways you take and what the result is. If neither works, make a staging copy of the site and put FTP and WordPress administrator access into the private area of this ticket, and we will look at it ourselves.

https://share.pluginus.net/image/i20230222134241.png
https://share.pluginus.net/image/i20230222134615.png