Bug #8699
closed
[J4] payment_fee database column failing to store during notification storage
Description
Looks like the mapping of notification data from basket isn't properly mapping payment_fee.
1366 - Incorrect decimal value for column ’#__cbsubs_notifications’.’payment_fee’ at row 1
This blocks notifications from being processed.
Updated by krileon over 3 years ago
Probably an empty string is attempting to be stored to payment_fee, which is a decimal column so that behavior isn't allowed in strict SQL mode.
Updated by beat over 3 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Looks like Paypal sent him a non-decimal value in `payment_fee` !
As `payment_fee` and `payment_gross` are not used in CB nor in any gateway (they are unused duplicates of `mc_fee` and `mc_gross`), I have simply removed them in
commit 1a5b917842ba793afa88f1ec1c53d91ff927bdde
I asked for the notification in the forum thread to check if other fields have similar issues.
Updated by beat over 3 years ago
The second issue of the thread is probably #8701, sovled in its commit 79d2edc53eeb3b175f53213b6b19b3314816a49e