Similar to #735, I have just experienced the same type of error, but coming from a different place in the code. It seems that we use similar logic is several places in regard to the points logs, and somehow we didn't realize that it wasn't completely fixed before. This time I experienced the error on the front of the site via the widget, whereas before I was only testing in the back-end, so maybe that is why.
We should identify all of the places where this logic is used, and fix all of them.
Similar to #735, I have just experienced the same type of error, but coming from a different place in the code. It seems that we use similar logic is several places in regard to the points logs, and somehow we didn't realize that it wasn't completely fixed before. This time I experienced the error on the front of the site via the widget, whereas before I was only testing in the back-end, so maybe that is why.
We should identify all of the places where this logic is used, and fix all of them.