Open philipdanielhayton opened 1 year ago
Did you every have a price / amount adjustment setup that you've since deleted? If this is the case, once you've created and used a price adjustment you shouldn't be deleting it as passed orders will attempt to deserialize their stored value into the right adjustment type and if that type has now gone, it will fail and error.
Ah ok things are starting to make sense. I haven't removed any but I have refactored the codebase which resulted in namespace changes.
I'll try updating the type
field in the database to the new namespace.
Yup, that's fixed it 👍🏻 Thanks for the quick reply Matt, as always.
Is it possible to make this more resilliant to codebase changes? It seems a bit tedious (and dangerous) having to manually update the database whenever the codebase changes. In my case I had only moved the class to a different folder to keep things clean as we added more adjustment types. Perhaps we could use alias via attribute decorators or something?
Anyway, thanks again for the swift reply, got me out of a right pickle!
Good thinking, I'll see what could be done here, and maybe at least throw a better exception.
Hi Matt,
There is an issue I've ran into on two separate projects that causes the Order Listing screen to fail whenever I try to access it. Unfortunately I'm not entirely sure what causes it, I realize this is not ideal for you to debug with so if there is anything further I can provide please let me now. Here's what I know for sure:
I'm guessing one of the orders has somehow ended up in an invalid state. I've had a quick scan through the orders table and nothing is jumping out at me. Is there anything in the soure code that could provide some clues for me to continue digging?
Value cannot be null. (Parameter 'type')