Profile: Boyko

Hi nopmstr2014,

You can add a custom widget zone and place it whenever you want in the markup. Here we have explained how to add a custom widget zone.
I don't know what html you have included but most probably you need to add some styling to it in order to be properly displayed in the different resolutions.

Hi naresh,

I guess you are talking about the skin of the carousel. The skin defines a css class that is put to the jcarousel element in the html and allows you to add styling for it. You do not need a separate .css file for it. You can define it in any .css file.
But you can't have different skins for different pages for a single carousel.
Once you define the skins for the carousel they are always present on any page the carousel is shown.

Hi joster,

There was an issue with the ActionFilter that populates the model but it is already fixed.
Please update the Fashion theme plugin .dll file. Please note that you need to update the Core plugin as well.

Hi beatmaster,

Thank you for the clarification!
I see now that this is could be misleading.
There are two important things here - the styling and the information.

About the styling I believe that you understand that this is a sample email and it doesn't mean that all emails will look this way. Please note that the email templates can be edited from the administration of the plugin, so you can style them in whatever way you want. We try to keep the default one as simple as possible and leave the customization to the customer.
For the image on the product page - our designer just wanted to make it looks good with the overall design of our new web site.

About the information - prior to nopCommerce 3.4 you couldn't modify the generated products with pictures html. So in nopCommerce 3.1 you can only have the picture with size 75 px and the product title below it (same as yours and our templates) . Since nopCommerce 3.4 we made the information in this token %ShoppingCart.ProductsWithPictures% to be editable in a separate view - AbandonedShoppingCartTemplate.cshtml. So now you can change the generated markup for the product information to whatever you want i.e have a bigger picture and place it on the left side and the product name on the right side etc. All the other information can also be show i.e price, short description etc. but it is not shown by default and if you want to show it you need to modify the AbandonedShoppingCartTemplate.cshtml view (coding skills required).

As it seems like you prefer the design shown on the product page and also to eliminate any misleading information we decided to change the layout of the products with pictures token. We will make it similar to the one on the product page but we can do this after the release of nopCommerce 3.5, which is expected next week and we will do it directly for nopCommerce 3.5.

Hi Ela,

I see now that you want to show images for the news items in the News page. This has nothing to do with the Mega Menu.
Unfortunalty in nopCommerce there is no way to associate an image with a news item, so this is not possible.

Hi swinstead,

We visited your web site and the logo url is the same as your web site's domain, which is correct as it should always point to the home page.
I guess it might have been some caching issue. You have probably accessed your web site via the IP of the server and the address has been cached.

Hi yves,

Thank you for the kind words!

The full text search seems to be working fine for us.
I would suggest you to try with the different options available in the nopCommerce administration before doing anything on the server.

Hi nopmstr2014,

We are not aware if such functionality exists in nopCommerce 3.4.

Hi Ela,

If you are talking about the links into the Mega Menu plugin to the News section then you can change them in this file the Views\MegaMenu\MegaMenu.cshtml file.
The code is like this:

if (Model.Settings.IncludeNewsLink)
    {
        <li>
            <a href="@Url.RouteUrl("NewsArchive")" title="@T("News")">@T("News")</a>
        </li>
    }

Hi digitalmbs,

We don't use any special formatting. We simply use the same token that is available in the plugin. I don't know why your formatting is different than ours. So it will be best if you can submit a ticket and add some screenshots, so that we can see what is wrong.