Filters Error after upgrade to 2.2.0

After upgrade the following issue started to occur when I try to apply a filter at the front-end:

Error: 0 - SQL=SELECT DISTINCT b.* FROM xxxxx_hikashop_product_category AS a LEFT JOIN xxxxx_hikashop_product AS b ON a.product_id=b.product_id WHERE b.product_published=1 AND b.product_type = 'main' AND a.category_id IN (18) AND b.product_quantity!=0 AND (b.product_access = 'all' OR b.product_access LIKE '%,9,%') AND (b.sizedresseu LIKE '%36%') ORDER BY filter_6 DESC LIMIT 0, 200

I have switched on debug mode, but no errors were detected.
My provider's server logs show no errors.
However, the Developer Tool in Google Chrome shows following lines:

Request URL:http://www.xxxxxxxx.com.ua/products/coats
Request Method:GET
Status Code:500 Internal Server Error
Request Headersview source


Do you have any idea?...

Hi Nocolas,

Thanks for very quick support!
I am actually using the latest version of Joomla (3.1.1 Stable).
I have changed MySQL to MySQLi under Global Configuration/Server/Database Settings.
I have enabled Debug System under Global Configuration/System.

Still I can't get a error. (It actually shows many wrapped text inside, but I can't see nothing special there.

I am quite sure it was working before the upgrade...

As for the link provided, I could not find location of file mysqli.diff... Definitely I don't understand something..
joomlacode.org/gf/project/joomla/tracker...racker_item_id=29345

Regards,

Another sort of error generated by filters:

Error: 1054 - Unknown column 'filter_6' in 'order clause' SQL=SELECT DISTINCT b.* FROM xxxxx_hikashop_product_category AS a LEFT JOIN xxxxx_hikashop_product AS b ON a.product_id=b.product_id INNER JOIN xxxxx_hikashop_category AS filter_22 ON filter_22.category_id=a.category_id AND b.product_manufacturer_id IN (17) WHERE b.product_published=1 AND b.product_type = 'main' AND a.category_id IN (12) AND b.product_quantity!=0 AND (b.product_access = 'all' OR b.product_access LIKE '%,9,%') ORDER BY filter_6 DESC LIMIT 0, 200

But this page does not generate any errors in the debug area as well (of course, Debug System is on...

Ooopph..
You are great guys there! I have localized the issue.

Whatever filter I try to select, it always shows me message Unknown column 'filter_6' in 'order clause'.
Filter with ID 6 is a simple sort by price.
After I have disabled that filter, everything works just fine!
I have created another sort-by-price filter with same settings and I have started to get same errors again.

I believe it is a bug. Please see my filter settings on the screenshot attached hereto.

Hi Nikolas,

I have sent a PM with admin credentials to you. Please, kindly check.

Regards,

Hi there,

I just took a look and it was a strange bug since there was a value in your session for this specific filter. After cleaning it, it's working fine.
Maybe you totally changed this filter after few try with another filter type (but on the same id) ending in causing this issue.
Anyway, tell us if it's fine on your end but I think it's ok now.

Hi Eliot,

A few clicks it was working. The next click it showed the same error again:

Error: 1054 - SQL Error Unknown column 'filter_6' in 'order clause'

SELECT DISTINCT b.* FROM xxxxx_hikashop_product_category AS a LEFT JOIN xxxxx_hikashop_product AS b ON a.product_id=b.product_id WHERE b.product_published=1 AND b.product_type = 'main' AND a.category_id IN (13) AND b.product_quantity!=0 AND (b.product_access = 'all' OR b.product_access LIKE '%,9,%') ORDER BY filter_6 DESC LIMIT 0, 200

Indeed, there was a real bug.
It took me a certain time but it's fixed!
For those who experience the same issue, you have to edit the file filter.php in administrator/components/com_hikashop/classes and change these lines:

if($filter->filter_options['title_position']=='inside'){
			$html.='<OPTION VALUE="'.$filter->filter_namekey.'">'.$filter->filter_name.'</OPTION>';

if($filter->filter_options['title_position']=='inside' && $filter->filter_data=='sort'){
			$html.='<OPTION VALUE="none">'.$filter->filter_name.'</OPTION>';

Hi Eliot,

The fix works!!
Thank you!

Regards