Did anything ever come of this? We are experiencing the same thing. Specifically with the Prisma theme. On the infinite scroll, looks like there's 4 separate ajax calls that sometimes just hang:
I should add we're using version 4.2.575.31113 of Nop Ajax Filters for nop 4.20.
Is there logic inside the widget component to only render if the slug matches a category slug? We have a custom route like "/my-route" that is configured to go to the Category action in the Catalog controller, but with some extra route values as well. When this page is rendered, the filters don't show up, but they work fine on regular category pages. Just wondering if it's because the widget doesn't recognize that it's on a category page. Any ideas to make that work?
On step 2 of the plugin docs, it says to install that package on your salesforce account, but when I click that link, I get this message:
"This app can't be installed.
There are problems that prevent this package from being installed.
Package Not Found The requested package doesn't yet exist or has been deleted. If this is a recently created package version, please try again in a few minutes or contact the package publisher."
I'm using a developer salesforce account for testing.
Also, for more info, I do see the <div class="nopAjaxFilters7Spikes"> placeholder but it is empty
I'm having the same issue, wouldn't the price filter at least be there if it works on the category pages? Also, I'm using the trial version if that matters.
For other people, to get the categoryId after the ajax is called, I used this...
var filterData = System.Web.Helpers.Json.Decode(Model.SpecificationFilterModel7SpikesJson);
product.CategoryId = filterData.CategoryId;
I added this block to the plugin's CategoryTemplate view, right before the call to the _ProductBox partial. This was the only way I could find to get the categoryId after the ajax call is made. Then the _ProductBox partial calls a child action that takes the productId and categoryId and just returns the PictureModel.