Recently viewed Carousel being cached

I have created a custom widget zone on the shopping cart page and created jCarousel with the source as "recently viewed products".
I have noticed that the carousel is being cached on the first view. So if the user goes to the shopping cart, then browses some more products. The carousel does not show the products viewed after the first time the cart was viewed.

I have placed this jCarousel on the product page (widget productdetails_bottom) it does update correctly there.

Hello,

What is the exact version of the JCarousel plugin you are using?

This is fixed in version 22375 of the plugin for nopCommerce 3.8.

I've got version 22320 at the moment. So I will try the latest version later on today or tomorrow.

So I am getting there. This is all on my development instance so its not affecting the live site.

The site uses the pavilion theme version 22320.
I downloaded the latest pavilion theme and I have installed the JCarousel plugin from it (by deleting the plugin folders (JCarousel and core) and copying the new plugin files over and restarting the w3p process). It looks to work well on the client side, but in the amdin portal I got an error when editing a jCarousel.

Method not found: 'Boolean SevenSpikes.Nop.Plugins.JCarousel.Models.JCarouselEntitySettingsModel.get_ShowProductsPrice()'.

I definitely restarted the w3p prcoess a number of times during this.

So next I uninstalled the jCarousel and reinstalled it. Now the admin panel appears to work correctly but I have lost all my configured carousels.

Is there a way I can get this working on live without uninstalling/reinstalling the JCarousel plugin? i.e. not loosing my carousels.


P.S. Is it an issue to install the latest SevenSpikes.core plugin without updating all the plugins?

OK, as an update to this,  have re-created the carousels and I can see the options for a carousel have changed quite a lot, so I assume it is old data causing the error.

I have one problem outstanding. I have lost my custom theme colours - (colour preset in the theme admin screen)

No matter what I do, they stay as the default #00a1b and f74258. None of the preset colours seem to work now. Is this something to do with the Core plugin version being different to the theme version?

Hello,

Did you try to clear the nopCommerce cache? If you are using bundling this will force the recreating the bundles. Also, if you are using CDN clear the CDN cache.

If you can't manage to resolve the problem please submit a ticket and provide admin credentials to your site.

Thank you!

I have this on my internal development machine so it is not easy to provide you access. I have done a search and the correct colour is in theme.custom-1.css and theme.custom-3.css but the wrong colours are in ThemeBundle.css

Head.cshtml references the other css files in that folder which all have the incorrect colours in. So I don't know where the theme.custom and ThemeBundle files are referenced.

Looking at the git history of this project, none of the files in  /Themes/Pavilion/Content/css
have changed.

Hello,

The bundling is nopCommerce functionality. Sometimes you have to force the nopCommerce to rebuild the bundles. Saving the theme settings and clearing the nopCommerce cache should recreate the bundle.

After some testing - including me seeing the bundled css was being updated, I have added a line to head.cshtml to explicitly bundle theme.custom-1.css and now it is working.

So this is good enough for me for now.

Could you confirm to me that it is OK to have a higher version of the SevenSpikes.Core plugin than some of the other plugins and the theme?

At the moment I have:

Core Plugin ver 28111
JCarousel Plugin ver 28111
All other plugins ver 22320
Pavilion Theme ver 22320

I have made quite a few customisations to the theme's razor and css files so It would be a bit of a job to upgrade it all.

Hello,

All of our plugins are depending on the Core plugin so it is recommended all plugins to be the same version as the Core plugin.

However, if you haven't noticed any problems it might be OK to use a higher version of the Core plugin than the other plugins.