Profile: iliyan.tanev

Hi,

This could cause an error if you select several more filter options when specific one is selected, because the other options can be disabled after specific filtration.
For example if you have this filter group:

Option A
Option B
Option C

After you click option A you may want to select Option B as well, but Option B may be unavailable after filtration which will cause error.

This is why we do not provide a way to do this.

Hi,

You need to replace the theme with the newest version, which you could find in the theme package and run all the upgrade scripts from 2.65 to 3.50. 
Please have your client raise a ticket and we will send them in the ticket.

Hi,

We broadcast nopAjaxFiltersFiltrationCompleteEvent on every filtration. Maybe you could use this event.

Hi,

Could you turn off your bundling so we could diagnose the Ajax requests ? 



The product field is not a dropdown it is an autocomplete search field. You must select a product in the first step and if you remove it later you could add something by typing its name in the search field. The autocomplete will generate a dropdown list with the matching results and when you select a product from the list it will appear above the product field.

Hi,

Are you using discount to remove the shipping or the Free shipping over 'X setting in Shipping Settings ? 

Hi,

Currently there is no plugin for nopCommerce that could give you that functionality. We are using this JS plugin to achieve this. Here is an article that could help you figure out how to use it.

Hi,

Actually when we return the filtered products we are using the PrepareProductOverviewModels, but with the default value of prepareSpecificationAttributes (which is false). We are not setting it to true, because it could represent a performance issue for some of our clients with huge number of specifications. 
If you want you could change it default value from CatalogController and this will affect the filtered products as well.

Hi,

Yes, you are right and that is why we would do everything we can to help you resolve this issue.

If you go to our Theme demo you will see that in IE 11 the Filters slider is working, also the QuickView and the AjaxCart are working fine too. 

The bug that you have described when you stop the script is because you have the bundling turned on, which means that you are stopping the execution of all the JavaScripts on the page and because both the AjaxCart and the QuickView JavaScripts are part of this bundled script they could not work.

The link you provided is taking the same time to load on IE 11 and on Chrome or Firefox. We, also profiled the JavaScript and this is the result. Keep in mind that your bundling is on, so this is the profile information for all the scripts that are executed on the home page, which includes the ones from nopCommerce as well, not only ours.
As you could see the execution time of all the scripts is 1,41s which is pretty fast considering the number of products that you have on your home page.

What I am trying to say is that nopCommerce is not the fastest platform, so these loading times are to be expected. Our theme has nothing to do with this. 
Our advice would be to consider reducing the number of products on your pages. For example instead of 30 you could show 15. This will speed up the loading time.

The only problem that we are seeing is that the Slider is loading slower than the products and menu, which is known bug and it is planned for resolving.

Hi,

You could uncheck the Disable Shopping Cart setting from RealOnePageCheckout -> Settings

Hi,

Maybe this thred on Arvix forum will be of help to you. Some of their users had a simular problem and there are some posible reasons that you could check.