Close

Profile: YashChandra

Avatar

User posts

12 years ago

Hi,

Sure you can remove this! However please note that if you would like to remove the Powered by nopCommerce line, you would need a copy right removal from nopCommerce. You can get it from here:

http://www.nopcommerce.com/p/1/nopcommerce-copyright-removal-key.aspx

I hope this is useful!

12 years ago

Hi Christoph,

This error is due to an inconsistency between the SevenSpikes.Core and the SevenSpikes.Nop.AjaxFilters. Did you replace both plugins? If so please restart your application and let us know if you still have this problem!

Best Regards

12 years ago

Hi,

We did schedule it to be fixed but it seems that we missed it for this release. So I would like to apologize for this oversight. We are looking at it right now and is the next thing we are going to do for the filters. I will let you know when we have a fix.
Just a little background, this issue is related to IE not obeying z-index rules and is actually quite tricky to solve. When you say IE 9, I believe you actually mean IE 9 and IE 8 compatibility views, as these are the only views in which we can reproduce it?
Anyways will keep you posted.

Best Regards

12 years ago

Hi Yves,

We found the problem. You set your Category Keywords Template to:

{name},buy ${name},${name} prices,${name} online

while it should have been:

${name},buy ${name},${name} prices,${name} online

This is hard to spot, as you can see. It is missing the dollar sign in front of the name token. The Nop Smart SEO cannot replace the {name}, because it looks for ${name} token and throws the exception you were seeing.

It should be working fine now. We tested it with a few categories and products. The special characters that you use in your product names and meta data should be fine and the Nop Smart SEO should work with them without problems.

Please let us know if you experience any other problems. But please do note that the tokens used in the SEO templates should be prefixed with a dollar sign.

Best Regards

12 years ago

Hi Yves,

We managed to reproduce the error. It does not seem to be random, because you can get it every time on this product:

http://www.usnautic.com/c/428/us-nauticcom-boat-mainteance-and-boat-care

We are not able to see the products in the admin area, due to restricted permissions. Would you be able to look at this product in the admin area and let us know if you see anything weird either in its name or its meta data like the keywords or the se-name.

In the mean time I am going to send you a .dll with debug info so that the exception in the log is more explicit.

Best Regards

12 years ago

Hi Yves,

Let me try it again on your site with a few refreshes of the page, to see what happens.

Best Regards,

12 years ago

Hi Yves,

We briefly enabled the Nop Smart SEO on your web site and checked this product that you mentioned:

http://www.usnautic.com/p/1008

It seems to be working fine. Maybe something has changed in your db in the mean time. Would you be able to point us to another page that breaks as a result of the plugin?

Thanks

Bugs
12 years ago

Hi,

This issue with the Gift Carts has been fixed. Now when you add a gift cart to the shopping cart from a category page you would be presented with a mini product details view where you can enter the gift card information.
You can download the new version from your My Account section on Nop-Templates.com.

Please let us know if you have any problems!

Thanks

Bugs
12 years ago

Hi iBEAUTHENTIC,

I think there has been a misunderstanding in this forum thread. We are sorry for this. So let me try to correct this.
According to our license point 1.1:

http://www.nop-templates.com/t/licensinginfo

You cannot use constituent parts of a product separately, which mean that you cannot extract the plugins from the theme and use them here and there on different web sites.

But this does not mean that you cannot use the theme for the basis of all your web sites. The plugins will work on every nopCommerce installation because they are standalone pieces intended to work with nopCommerce. What the support team meant by "will not work" is that they are styled only for the fashion theme. Styling includes front end work (changes to the razor and the css). The razor and css files are open to modifications, so you can change them as much as you would like, when you decide to change the styling of the theme. In other words if you change the styling of the theme you can also change the styling of the plugins. The View in List functionality is just something that is removed from the product result razor view of the filters so that the filters can work in the Fashion Theme which does not have a View in List, but should you need to use it you can always add it back to razor and the filters will work with it.

In summary, let me say, that the theme is open to modifications which includes the plugins. So you can change it as much as you would like (theme and plugins) in order to use it for different web sites.

Please let us know if my explanation is not clear or if you have additional questions.

Thanks

12 years ago

Hi,

Thanks for the suggestions! Such feedback is greatly appreciated by us, as it helps improve our products in a way that customers can benefit from.

I think 1. is mandatory to be implemented and we intend to do it with the next release.
3. is very useful although not straightforward to do as it will require database changes. However we will definitely consider it.
4. we will investigate for the next release, although it seems to require the use of the price calculation service in nopCommerce and this could lead to performance problems with the price range filter.
2. seems seems a bit specific at the moment, although I could think of a few web sites that have this type of filtering. It should be easy to implement, so again this will go on our list of features to consider.

All in all, only 4 seems like a bit of a problem for now. But everything else is quite good! So thanks again.
Please note that by next release I mean for the next version of nopCommerce, which is 2.4.