[Ernest Marcinko]

Yes, of course! You can find it here: https://i.imgur.com/sbsxHvJ.png

[Ernest Marcinko]

Oh, I’m sorry, I missunderstood you. This is what you are looking for: https://i.imgur.com/1PoesXN.png
Increase it to as much as you like, I usually recommend 100 max for the best user experience.

[Ernest Marcinko]

You are very welcome!

Sure, make sure the search override is enabled: https://i.imgur.com/AHxgZvH.png
That should do the trick 🙂

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi,

I’m afraid results separation this way is not possible to do. It’s not because of the search plugin, but generally this is not possible only by using different kinds of widgets, because all of them will simply use the same query output. Elementor will not separate them, all of them will simply output the same thing. Even if it worked, their pagination would be broken, as potentially non-existing pages of results could appear.

Unless you are a very experienced programmer, I would not recommend doing this. In the past 12 years I have only seend 2 or 3 cases where they were able to build a custom grouped results page, and all of them were custom coded from top to bottom, as this is not possible simply via page builders.

Usually I suggest a custom code where I can, but this is far far more complicated than that, and it is not because of the search plugin either.

I recommend using either of those widgets – the posts widget works the best all around for all types of content. Another, perhaps even better possibility is to have multiple search bars for multiple types of a results and multiple results pages.

I wish this was possible, I know a few of my customers who would love this separated results page.

[Ernest Marcinko]

Hi,

Sure, let me help you with that! I recommend checking the filters related documentation as well, but here are the exact steps:

– First off, to make things a bit simpler, set the Frontend Search Settings general options like so: https://i.imgur.com/6TcRj8w.png
– Then click to the Categories and taxonomy terms panel and choose all from categories: https://i.imgur.com/QgNIzEM.png
– Then click the Change Display Mode and change it to drop-down mode: https://i.imgur.com/c6ZBc0g.png
– Now, go to the Post Tags filter, and do similarly: https://i.imgur.com/drcxeBw.png
– Let’s disable the search bar, as you don’t need it: https://i.imgur.com/e1ejZWC.png
– I also like to turn off this option so the results doesn’t close: https://i.imgur.com/EUrQIhz.png

Now, if you check on the preview window, you get the two-drop downs with the results: https://i.imgur.com/s6DK4Qe.png

To take it even further, you can use the search + the results shortcode (or editor blocks) to move the settings and the results container wherever you want on the same page to be displayed separately:

[wd_asp id=1]

and for the results:

[wpdreams_asp_settings id=1]

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Hi!

The feature is under construction, as some back-end settings changes have to be implemented first. I know that some search plugins offer conditional filters, but in most casses there is a terrible performance caveat when the posts number rises – usually only examples with a very few products are shown for that reason, and we want to make sure this works correctly even on a higher post count.

That being said I don’t know the expected date on this, but it’s a very high priority feature, so it’s definitely coming as soon as possible.

[Ernest Marcinko]

Hi!

You can hide that switch with this option: https://i.imgur.com/HZfUXCd.png

As for the filters, the answer is it depends. By default an unchecked checkbox is considered an exclusion + items which have no relation to that taxonomy are also displayed. In most cases this default behavior is expected.

In your case I suspect you want to show items which strictly match any of the categories and also hide anything else. In that case this is the configuration you are looking for: https://i.imgur.com/fR60hXS.png

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

You cannot access this content.

[Ernest Marcinko]

Oh, it was you indeed, I didn’t even notice I’m so sorry.

In that case, this must be adjusted from the script, maybe it’s possible with just a tiny bit of modification.

I have made an issue request on this one. It’s basically almost there, so it needs a bit of work and testing, but I’m sure it’s only missing something tiny for the quantity to work. It’s going to be added in the upcoming release within 2 weeks.

Until then, can you please try this modified script version:

jQuery(function (t) {
	if ("undefined" == typeof wc_add_to_cart_params) return !1;
	var a = function () {
		t(".asp_r")
			.on("click", ".add_to_cart_button", this.onAddToCart)
			.on("click", ".remove_from_cart_button", this.onRemoveFromCart)
			.on("added_to_cart", this.updateButton)
			.on("added_to_cart", this.updateCartPage)
			.on("added_to_cart removed_from_cart", this.updateFragments);
	};
	(a.prototype.onAddToCart = function (a) {
		var o = t(this);
		if (o.is(".ajax_add_to_cart")) {
			if (!o.attr("data-product_id")) return !0;
			a.preventDefault(), o.removeClass("added"), o.addClass("loading");
			var r = {};
			r.quantity = parseInt( o.closest('.woocommerce').find('input[name=quantity]').val() || 1 );
			t.each(o.data(), function (t, a) {
				r[t] = a;
			}),
				t(document.body).trigger("adding_to_cart", [o, r]),
				t.post(wc_add_to_cart_params.wc_ajax_url.toString().replace("%%endpoint%%", "add_to_cart"), r, function (a) {
					a &&
					(a.error && a.product_url
						? (window.location = a.product_url)
						: "yes" !== wc_add_to_cart_params.cart_redirect_after_add
							? t(document.body).trigger("added_to_cart", [a.fragments, a.cart_hash, o])
							: (window.location = wc_add_to_cart_params.cart_url));
				});
		}
	}),
		(a.prototype.onRemoveFromCart = function (a) {
			var o = t(this),
				r = o.closest(".woocommerce-mini-cart-item");
			a.preventDefault(),
				r.block({ message: null, overlayCSS: { opacity: 0.6 } }),
				t
					.post(wc_add_to_cart_params.wc_ajax_url.toString().replace("%%endpoint%%", "remove_from_cart"), { cart_item_key: o.data("cart_item_key") }, function (a) {
						a && a.fragments ? t(document.body).trigger("removed_from_cart", [a.fragments, a.cart_hash, o]) : (window.location = o.attr("href"));
					})
					.fail(function () {
						window.location = o.attr("href");
					});
		}),
		(a.prototype.updateButton = function (a, o, r, e) {
			(e = void 0 !== e && e) &&
			(e.removeClass("loading"),
				e.addClass("added"),
			wc_add_to_cart_params.is_cart ||
			0 !== e.parent().find(".added_to_cart").length ||
			e.after(' <a href="' + wc_add_to_cart_params.cart_url + '" class="added_to_cart wc-forward" title="' + wc_add_to_cart_params.i18n_view_cart + '">' + wc_add_to_cart_params.i18n_view_cart + "</a>"),
				t(document.body).trigger("wc_cart_button_updated", [e]));
		}),
		(a.prototype.updateCartPage = function () {
			var a = window.location.toString().replace("add-to-cart", "added-to-cart");
			t(".shop_table.cart").load(a + " .shop_table.cart:eq(0) > *", function () {
				t(".shop_table.cart").stop(!0).css("opacity", "1").unblock(), t(document.body).trigger("cart_page_refreshed");
			}),
				t(".cart_totals").load(a + " .cart_totals:eq(0) > *", function () {
					t(".cart_totals").stop(!0).css("opacity", "1").unblock(), t(document.body).trigger("cart_totals_refreshed");
				});
		}),
		(a.prototype.updateFragments = function (a, o) {
			o &&
			(t.each(o, function (a) {
				t(a)
					.addClass("updating")
					.fadeTo("400", "0.6")
					.block({ message: null, overlayCSS: { opacity: 0.6 } });
			}),
				t.each(o, function (a, o) {
					t(a).replaceWith(o), t(a).stop(!0).css("opacity", "1").unblock();
				}),
				t(document.body).trigger("wc_fragments_loaded"));
		}),
		new a();
});

[Ernest Marcinko]

You cannot access this content.

[Author]

Posts