Yes, of course it works wrongly, because after you apply a filtering, VM Custom Filter Pro try to load the category using the default VM layout (not even MaterialMart's default layout), but you actually uses "flexv2" layout from the MaterialMart. I am sorry but i can't provide you a solution about this problem, my knowledge is limited because this is their plugin. You should talk to the custom filter pro developers; and ask them, why custom filtering doesn't use the layout file from the template override folder (/templates/YOUR_TEMPLATE/html/com_virtuemart/category/)
By the way, after you manages to display MaterialMArt's flexv2 layout or MaterialMArt's default layout on the category page; you should also talk to them, and say exactly this below (they would understand):
- After the AJAX requested is completed, as a callback, these lines below should be called to re-init the MaterialMArt's JavaScript events on the category page:
jQuery.fn.initMaterialMartEvents();
jQuery('.FlexibleSwitchButtons a.switch_thumb3').addClass('switch_active');
jQuery('.FlexibleSwitchButtons a').click(function(e){
e.preventDefault();
jQuery('.FlexibleSwitchButtons a').removeClass('switch_active');
jQuery(this).addClass('switch_active');
var target = '.'+jQuery(this).attr('rel');
jQuery('.flexibleProductsContainer').fadeOut('fast', function() {
jQuery('.flexibleProductsContainer > div').hide();
jQuery('.flexibleProductsContainer ' + target).show();
jQuery('.flexibleProductsContainer').fadeIn('fast');
});
});
// Because these lines above will re-init the JavaScript events of MaterialMart after the category page gets reloaded via AJAX. Such as; switchBtn (grid,list,multi), fancy dropdown, quickLook popup etc..