Project

General

Profile

Actions
Copy link

Bug #8699

closed

[J4] payment_fee database column failing to store during notification storage

Added by krileon about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
beat
Target version:
4.5.3
Start date:
07 September 2021
Due date:
% Done:

100%

Estimated time:

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.

https://www.joomlapolis.com/forum/255-developer-members-support/244294-j4-cb-subs-possible-bug-with-error-code-1366#326296

Actions
Copy link
 #1

Updated by krileon about 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.

Actions
Copy link
 #2

Updated by beat about 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.

Actions
Copy link
 #3

Updated by beat about 3 years ago

The second issue of the thread is probably #8701, sovled in its commit 79d2edc53eeb3b175f53213b6b19b3314816a49e

Actions
Copy link
 #4

Updated by beat almost 3 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF