Profile: SDobrev

Hello Travis,

Could you please provide a URL to your store where we can investigate this problem?

Thank you.

Hi,

All products will be upgraded to 4.00 after the official nopCommerce 4.00 release.

Which version are you using? We have updated the plugin and now the performance is improved.

If you are using the latest version of the plugin for nopCommerce 3.80 or 3.90 you can limit the shops in the shops' list by a small customization in the JS files. On the map, all shops will be visible.

Please note the search by tag and by distance will work only with the visible shops (in your case only 50 shops).

Hi Giampiero,

Here is an example:

private IMyService _myService;

public IMyService MyService
{
    get
    {
        if (_myService == null)
        {
            _myService = EngineContext.Current.Resolve<IMyService>();
        }

        return _myService;
    }
}

Hi,

Have you made any custom modifications? Most probably the ShoppingCartController constructor is changed.

If this is the case you will have to revert your changes and use property injection instead of constructor injection.

Hi Travis,

Could you check which customers are generating this error? If you open the full error page you will see it.

It is possible this errors to be generated by Search engines/bots.

Hi,

Which filters have you enabled? It is possible the new products don't have specification/attribute options.

Please submit a ticket with more information.

Hi,

If you are using CDN clear the cache. It is possible to receive this error because the cache of your customers' browsers is not cleared yet.

Please note that it is not a good idea to modify the code.

Hi,

In nopCommerce 3.9 the special price is replaced by a Tier Price with quantity 1.

Hi,

Most probably the old JS files were cached by your customers' browsers and this is the reason for the errors in the log. Now the cache is expired and they use the new version.

By changing the dlls do you mean that you changed the code somehow?

Hi,

The AjaxFilters is the same version as the Core plugin so the problem is somewhere else.

Try to uninstall and install the AjaxFilters and if this does not help please clear the Temporary ASP .NET files.