Jeckstart

So here’s simple js solution which works for me
(the only bad thing is, you have to specify taxonomy slug in there, or at least part of it)

// 1.Get query string
var qs = (function(a) {
	if (a == "") return {};
	var b = {};
	for (var i = 0; i < a.length; ++i)
	{
		var p=a[i].split('=', 2);
		if (p.length == 1)
			b[p[0]] = "";
		else
			b[p[0]] = decodeURIComponent(p[1].replace(/\+/g, " "));
	}
	return b;
})(window.location.search.substr(1).split('&'));

// 2.Store needed keys in woocommerce's html
for (var key in qs)
{
	if( key.indexOf('pa_') == 0 || key == 'stock' || key == 'swoof' ||
		key == 'YOUR_TAXONOMY' )
	{
		$( ".price_slider_wrapper .price_slider_amount" ).append('<input type="hidden" value="' + qs[key] + '" name="' + key + '">')
	}
}

Seriously, I don’t understand logic of these people.

This is not-even-tenth time I encounter this, and I don’t understand why do they force us to write complicated on-top js’s to fix some simple thing, instead of just letting us edit one string in core file which would totally fix the problem

Just noticed, that categories filters work nice with your filters also.
So things that do not work are: taxonomies, attributes, “in stock”.

So for example, if my url was:
store?swoof=1&min_price=742&max_price=15477&product_cat=bodi-teddi&pa_color=purple
After price filter has been applied (re-applied, in this case) it becomes:
store?min_price=581&max_price=15477&product_cat=bodi-teddi

Hi, really nice awesome plugin you made!
But I have this conflict with woocommerce price filter, too (in v1.0.5)
They work fine together only for “product tags”;
For anything else (taxonomies, attributes, “in stock”) after woocommerce price filter is applied, all previosly applied filters disappear (“swoof=1” is erased from url also).
BUT I have noticed backwards compatibility – if I use your filters after woocommerce price filter is applied, everything is fine!

Can you please hint me what may cause the problem? I think I will be able to fix it, if you point me in right direction ??

Jesus Christ i just forgot to flush links again..
Works fine! Thank you!

I didnt know, but qTranslate is actually no longer supported for new WordPress;
it is adviced to use mTranslate instead
..and it solved the problem.

well alright, another outdated plugin (qTranslate) causes pain in ass TT
resolved then

It works from login widget in header (which confirms that networks are indeed configured right)
But it doesn’t work from profile page (same gray page every time)
My thoughts – in plugin settings you can configure “redirect after login from widget”, I set it to “Homepage (default)” and it works. But for “login from profile page” – there is no such setting, so I can’t make it “redirect to homepage”. Maybe this is the cause?

Sorry I actually managed to do it with filters xD
my bad

People on the internet say it isn’t possible at all, btw

Ye thank you, it works like charm!
I have no redirect you are talking bout, so its even better ??

Ye I thought so ;p thanks for good slider anywayz)

No sorry, the problem is solved, it was that specific theme’s fault – conflict between different jqueries – the new one required by slider and the old one required by old theme’s features

Solution didn’t come fast though, its so hard to make different versions of jquery libraries love each other ??