Profile: iliyan.tanev

Hi Rob,

The UrlRecord helper needs valid route name to work. The "Topic" route name is not valid in this case, the example comment is not updated, sorry for that.

The simplest thing you could do in this case is to write something like:
<li><a href="/Search engine friendly page name">@T("Some resource")</a></li>

Hope this helps!

Regards

Hi TOMSUOYAI,

By master page I suppose you mean the Layout.
For example if you go to the TopicDetails view in Nop.Web on top you will see the Layout variable.
Maybe this is the view you are looking for.

Hope this helps!

Regards

Hi SHELLYSHAO,

Ajax Filters work with feature products. All you need to do in order to enable the functionality is to set the includefeaturedproductsinnormallists setting to true from the administration.

Here you can see a video of how to modify settings.

Hope this helps!

Regards

Hi CWJACKSON,

I was unable to reproduce the problem on clean instalation.
I suppose you are using the Nop-Commerce (Source code) version. Could you make sure you are copying the plugin folders to \Presentation\Nop.Web\Plugins ?

Regards

Hi ASANAIQCAMP,

Unfortunately the "Price Range Filter" takes only the basic and special price of the product and ignores the other prices applied to it, except the taxes. This will complicate the plugin a lot and it will, probably slow it down, thats why it is not supported. But if you want you could suggest this to our User voice portal.

Regards

Hi ASWAAQ,

For the moment our filters does not support this as nopCommerce doesn't support any kind of paging or filtering on all manufacturers page.
Maybe it will be best to suggest it to NopCommerce team.

Regards

Hi ASWAAQ,

Currently this functionality is not supported.

I suppose you mean the View as, Sort by and Display per page filters.
Could you discribe in more detail why do you want this ? Maybe it will be a gread feature to be added to filters in the future.

Regards

Hi GNIKSPAM,

Probably the problem is caused by left over tables in the database that reference the tab Id from the 'SS_QT_Tab' table.

I suppose you have upgraded from 3.2 to 3.3.
Have you run the upgrade script and did it finish withouth errors ?

If everything went ok, posible solution would be to go to your database and delete each table with 'SS_QT' prefix.

Let me know if this helps.

Regards

Hi OAKSTONE,

Could you tell me whitch version of the plugin are you using ?

The best solution would be to upgrade the Core plugin, the Filters and The Theme.

Please let me know if this helps.

Regards

Hi ASWAAQ,

This happens on default clean too, so I guess this is some kind of nop issue.

Posible fix would be to capture the click event of the buttons and to use something like this to fix the scroll to top.

Hope this helps!