I am having this problem from Magento 2.2.5 and when upgraded to Magento 2.3 also. I use custom template

Layered navigation with Ajax isn't working. I use Amasty one

It just refreshes the page and no products is called.

If I disable Ajax everything is fine. I can't give more details because I don't have any errors in console, nor in log files. I am having two days now and I can't find anything.

Any help what to check would be much appreciated

2 Answers 2


Problem solved. I will describe for others with same template and extension. Main problem was that the response was not coming in json format, just plain html, and js code trying to work with it like with json and fails.

This was because both modules amasty and mgs panel rewrite this controller


MGS theme is written like this:

It has a MGS layered module which was working like amasty. first time page loading go throw MGS layout and layer ajax is going throw Amasty. All scripts for quick view add to cart and other worked only once on page load, and it not affecting to the products after filter. I guess old script for MGS had to restart all scripts after filter action.

So when I went to this file:


and comment out this line:

<preference for="Magento\Catalog\Controller\Category\View" type="MGS\Mpanel\Controller\Category\View" />

But this broke all js scripts like add to cart etc...

So I check further and I got this solution:

In file:


just below this line:

if ($.mage.amShopbyApplyFilters) { 

added this:

var formKey = $("input[name*='form_key']").first().val();

              $(".mgs-quickview").bind("click", function() {
                var b = $(this).attr("data-quickview-url");
                b.length && reInitQuickview($, b)

              $("img.lazy").unveil(25, function(){
                var self = $(this);
                     }, 0);

And bingo. Everything fixed. Till now it is working.


The info you have given is extremely brief so only expect brief answers.

It sounds like your layered navigation template customisations have affected it, can you revert to the core templates one by one and see which one is the breaking change?

Then work your way through the code to determine which change in that template affected it.

  • you are absolutely right about the information I have given. But I don't have much. I will try your way... I did some revert to core template but without success.....I'll try again
    – G. G.
    Feb 28, 2019 at 16:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.