Hello @cleanpagedesign ,
By checking locally I have found no issue. It seems the issue is happening to your site only. There might be some conflict issues with other plugins/themes. Initially, you can follow this link to check for the conflicts.
You can contact our technical support engineers by submitting a ticket Here. They will check your site and let you know what is causing this issue.
Best Regards!
OK, thanks. I deactivated all plugins (expect for WePOS and Woo) and the error persists.
I’ll try a support ticket and see if I can get to the bottom of it.
Dom
@cleanpagedesign did you manage to resolve this issue? I too am getting the same error once the order is placed.
@intelcoders Hi there. I tried a couple of things and seem to have resolved it, but I haven’t tested it in the real world yet; only on a staging site – but I’ve gone back to it several times and tried in a private browser etc to make sure it wasn’t a one-off.
First thing to say was that I deactivated everything except Woo and WePOS and reverted to the TwentyTwentyOne Theme and I was still receiving the error – so I figured it wasn’t a conflict.
Next thing I did was make sure the /wepos/ URLs (think there’s a /wepos/ and a /wepos/#) were excluded from the cache. The other thing I tried was assigning a sale to a registered user (a test one I had set up). One or the other, or both, of these things appear to have resolved the issue. I suspect it’s the cache, but if it is the user thing, what I thought I could do is to set up a dummy user eg “POS User” and then assign cash sales to them.
@cleanpagedesign Thanks for the pointers, will try doing the same.
