Profile: Support

Hi,

Thank you for reporting this. It seems that the class has been renamed in nopCommerce 2.65. It is fixed now and you can download the latest version of the theme and update the styles.css file.

Many thanks

Hi IndigoTea,

We are glad that someone asked this specific questions, which means that you guys are doing the modification of the themes in proper way. Namely to copy it over with a different name and then apply your modifications in the new theme.
You also need to do this for each plugins as all plugins have a Themes folder where the specific views are placed. This way you can have more than a single theme running on the same instance of nopCommerce i.e DarkOrange, Fashion etc. We don't recommend doing this on a production environment but it is very convenient during development and making modifications to a new theme.

Basically you need to add your new name of the Fashion theme i.e FashionNew to the supported theme names setting.
So here is a little background information why you need to do this and how.
The Fashion theme plugin dynamically adds some new data to the model aka productFashionModel via an Action Filter. But we don't want to add this additional information to the product model if we are running a different theme and want it only for the Fashion theme. That's why there is a setting that specifies a list of themes for which we want this additional information.
Here is the setting you need to modify:
SevenSpikesSettings.FashionThemeNames
The value of this setting should be "Fashion" as you can see in the Settings.xml file of the Fashion theme plugin. You need to add your new theme names separated with semicolomn ";". For example:
"Fashion;FashionNew"

When you add your new theme name then you will get the product manufacturers and categories on the product page when running the modified version of the Fashion theme.
We will add a check if the product fashion model is not null, so that you don't get this error on the product page if you forget to add the theme name although you will lose this additional information if you forgot to do so.

Best Regards,
Nop-Templates Support Team

Hi Tommy,

No, the fashion theme for 2.6 won't run with fluent validator 3.4.0.0 just like the nopCommerce 2.6 won't run with it without rebuilding the whole sources with the new version. If we upgrade version 2.6 to work with Fluent Validator 3.4 then all our clients that have nopCommerce 2.6 installed won't be able to run the Fashion theme on it.
You should use version 2.65 of nopCommerce and version 2.65 of the Fashion theme. The upgrade is quite easy. You need to run the upgrade script for nopCommerce 2.65, then run the new nopCommerce 2.65 and the new version of the Fashion theme and the plugins for 2.65.

Best Regards,

Please use the homepage_top widget zone and this way the JCarousel will be shown only on the Home page. The content_before is a widget zone defined in the master layout, so it is available on every page on your store.
You can define you own custom zone and place it whatever you want on the Home page.
If you want to show it outside the content of the Home page you can define your own section and show it in the _root.cshtml file if it is defined.
@if (IsSectionDefined("YourSectionForJCarousel"))
{
    @RenderSection("YourSectionForJCarousel")
}

Then define the section in your home page Index.cshtml file:

@section YourSectionForJCarousel
{
    @Html.Action("WidgetsByZone", "Widget", new { widgetZone = "home_page_top_jcarousel" })
}

You can see the documentation of the Electronic theme for the Main slider as this is how we place it on the top.

Hope this helps!

Best Regards,
Nop-Templates Support Team

Hi joster,

There is no need to run any upgrade scripts on a clean install.
If you rebuild your solution or modify your Global.asax file will fix this as this will make MVC to find the new controllers of the plugins (Global.asax is modified internally when a new plugin is installed but it doesn't always work) and find the Settings pages in the administration respectfully. You mention that the Save doesn't work. Can you specify which Save is not working i.e for which plugin?

We have't tried nopCommerce with SQL Azure. Is there a separate branch of nopCommerce or it is the regular branch but it can also work on Azure.

The cart pages should work as the theme is upgrade for nopCommerce 2.65.
What is the error you receive?

Update:We just noticed that the Add to Cart button on a category page is not working right after a clean installation but once we go to a product page it is working fine. That is quite strange and we will investigate it. Please let us know if you have any problems with the Ajax Cart. Maybe Ctrl + F5 is required to update the browser cache.

Best Regards,
Nop-Templates Support Team

Hi Jon,

All out products are already available for the just released nopCommerce 2.65 version.

Best Regards,
Nop-Templates Team

Hi,

Thank you for pointing this out. We will double check why the code has been commented (probably by mistake).

Best Regards,
Nop-Templates Support Team

Hi Paulo,

Thank you for reporting this. It has been fixed now. You need to download the package again and update this file:
Themes\Electronics\Content\style.css

Alternatively you can simply remove
overflow:hidden
from this css class
.product-pager-and-sorter-and-view-options-7Spikes .product-pager-and-size
on line 3140.

Best Regards,
Nop-Templates Support Team

Hi Jon,

We are aware of this issue with the FluentValidator.dll and .NET 4.5.
So we will release a new version for all our plugins for nopCommerce 2.65, which is to be released tomorrow or Friday.
We are not going to rebuild our plugins for nopCommerce 2.6 with the new FluentValidator version because all our clients that use nopCommerce 2.6 will not be able to run them as nopCommerce 2.6 uses the old version of FluentValidator.
Also not all clients will want to upgrade to 2.65 as not all of them use shared hosting and are not going to move to .NET 4.5.

So once the nopCommerce 2.65 is released you can download our plugins for nopCommerce 2.65.
We hope this works for you!

Best Regards,
Nop-Templates Support Team

Hi moiraeman,

Thank you for the proposal!

Yes, we can. Let's first see how many people will vote for it as it is an indication for us that it is going to be a really useful feature.

All the best,
Nop-Templates Team