Ah that would explain it - Thanks as always!

Hi Matt,

Can you explain a little bit about how the caching now works since the upgrade from 1.6 -> 1.7 please?

Since the upgrade I'm finding that my cart is not displaying any updates that are made to it, unless I force a recompile, which leads me to think that I am not forcing an update on the cache when I am making changes to the order.

Thanks,

Paul.

Hey Paul,

It's a pretty fundamental change TBH. We swapped out the whole caching mechanism for a custom one that allows sliding expiration. Before we were just caching into Umbraco's own cache, but we needed more control over the cache so had to implement our own (though it's based technically on how the Umbraco isolated caches work).

Hmm, if you are needing to restart the app pool to see the changes then it would suggest the changes are being made but the cache isn't updating for some reason.

I'll have to give this a test.

Matt

I've just tested on my local build and the orders seem to be updating OK in the checkout pages. I can increase/decrease quantities and remove items from the cart and all seems to update as expected.

Are there any errors in your trace log?

Matt

Matt,

Nothing in the trace log.

Because I am handling all cart updates in ajax I can see that it is passing updated order data back to the client (and then updating the totals etc as I would expect).

If I then refresh the page it reverts back to the previous values, as though it has not saved the order. Restarting the app pool and then refreshing after this does display the updated order data.

I have a couple of extension methods that I am using to add a product:

    public static BasketData AddItem(this OrderReadOnly orderRO, string productReference, decimal quantity)
    {
        using (var uow = VendrApi.Instance.Uow.Create())
        {
            var ret = orderRO.AsWritable(uow)
                .AddProduct(productReference.GetProductSnapshot(), quantity, null, "", "", null)
                .CompleteBasketAction(uow, BasketData.BasketAction.AddItem);
            ret.SetProduct(productReference);
            return ret;
        }
    }

    public static BasketData CompleteBasketAction(this Order order, IUnitOfWork uow, BasketData.BasketAction action)
    {

        //To do - Run basket checks...
        VendrApi.Instance.SaveOrder(order);
        uow.Complete();
        return new BasketData(action, order);
    }

Is there anything that jumps out as to why this wouldn't work?

I have also tries putting the uow.Complete() within the using statement rather than trying to pass the UOW as a parameter and the result is the same.

Do you have any front end caching in play at all? And what is your code for retrieving the order initially on page load?

The AddProduct call seems kind of odd having to pass the snapshot and the null params. I think if you add a using Vendr.Core; statement at the top you'll get access to some more useful AddProduct extension methods where you won't have to supply those. Not sure this is the root of your issue though.

Matt

I think those null parameters and empty strings are just a throwback to something I was doing previously, I have removed those now, with no effect.

The only caching will be the default out of the box settings, as I have not changed anything.

I'm using the following to get the order on page load...

public class TopNav : ViewModelBase
{
    public int BasketQty = 0;
    public bool BasketError = false;
    public string BasketTotal = "";
    public OrderReadOnly Order;
    public TopNav(IPublishedContent content) : base(content)
    {
        Order = VendrApi.Instance.GetOrCreateCurrentOrder(StoreId);
        BasketQty = 0;
        BasketError = false;
        BasketTotal = new Price(0, 0, Order.CurrencyId).Formatted().ToString();
        if (Order != null && (int)Order.TotalQuantity > 0)
        {
            BasketQty = (int)Order.TotalQuantity;
            BasketTotal = Order.SubtotalPrice.Value.Formatted().WithTax.ToString();
            BasketError = !Order.OrderCanProceed();
        }
    }
}

Hmm, that seems OK to me 🤔

I'm not sure why it's working for me then and not you. Short of getting you to send me your project I'm not sure how else to debug this 🤔

Matt

Hey Paul,

Yea, seems ok to me.

Without debugging into what is actually happening and when things are actually changing I'm not sure what to suggest.

You could try accessing the ICacheAccessor in Vendr and look in the EntityCaches for the order cache and check to see if it's getting added into the cache once the UoW transaction is complete.

Effectively how our caching works within transactions is we have a global cache, then in a transaction, any changes to the cache are made to a temporary cache, then when the transaction completes, all the changed items in the temporary cache are copied over to the global cache. So if you can follow that flow you can check it's actually doing what it's supposed to do.

Matt

Sorry Matt, Can you just give a really quick starting point as to how I could access the ICacheAccessor please?

Hi Paul,

Sure, add ICacheAccessor as a parameter on your controllers constructor, then store it in a private readonly var. Then check it's EntityCaches property for the order cache and see if your updated order is in there and up to date.

Matt

So would I get the Order cache by

var c = _cache.EntityCaches.GetOrCreate<Order>();

?

Not quite. All entities have an internal object that holds their state so for orders that OrderState

var c = _cache.EntityCaches.GetOrCreate<OrderState>();

Matt

Well, it's telling you that the cache isn't getting updated so something is stopping it

I'm kinda back to where I was earlier now though and really I think the only way I can get to the issue is if I can debug the project for myself and see what the problem is.

Does the project contain any sensitive information? Would it be zippable so I can test it? You can send a link to [email protected].