Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.3.1
-
Component/s: None
-
Labels:None
Description
Someone reported that calling Packages::add via the API without specifying a currency for pricing information led to an SQL error:
SQLSTATE[21000]: Cardinality violation: 1241 Operand should contain 1 column(s)
While unable to duplicate that error specifically, the cause appears to be related to currency rule validation. Attempting to add a package without specifying a currency for pricing leads to an Illegal Offset Type error when attempting to format prices into the non-given currency.
When formatting a currency, the currency type should be checked. Likewise, the rules for adding/editing a package should be updated to require a currency to be set.
Issue Links
- relates to
-
CORE-1528
Removing a package pricing row may lead to error: "Currency code must be 3 characters"
-
- Closed
-
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
| Description |
Someone reported that calling Packages::add via the API without specifying a currency for pricing information led to an SQL error:
SQLSTATE[21000]: Cardinality violation: 1241 Operand should contain 1 column(s) While unable to duplicate that error specifically, the cause appears to be related to currency rule validation. When formatting a currency, the currency type should be checked. Likewise, the rules for adding/editing a package should be updated to require a currency to be set |
Someone reported that calling Packages::add via the API without specifying a currency for pricing information led to an SQL error:
SQLSTATE[21000]: Cardinality violation: 1241 Operand should contain 1 column(s) While unable to duplicate that error specifically, the cause appears to be related to currency rule validation. Attempting to add a package without specifying a currency for pricing leads to an Illegal Offset Type error When formatting a currency, the currency type should be checked. Likewise, the rules for adding/editing a package should be updated to require a currency to be set |
Tyson Phillips (Inactive)
made changes -
| Description |
Someone reported that calling Packages::add via the API without specifying a currency for pricing information led to an SQL error:
SQLSTATE[21000]: Cardinality violation: 1241 Operand should contain 1 column(s) While unable to duplicate that error specifically, the cause appears to be related to currency rule validation. Attempting to add a package without specifying a currency for pricing leads to an Illegal Offset Type error When formatting a currency, the currency type should be checked. Likewise, the rules for adding/editing a package should be updated to require a currency to be set |
Someone reported that calling Packages::add via the API without specifying a currency for pricing information led to an SQL error:
SQLSTATE[21000]: Cardinality violation: 1241 Operand should contain 1 column(s) While unable to duplicate that error specifically, the cause appears to be related to currency rule validation. Attempting to add a package without specifying a currency for pricing leads to an Illegal Offset Type error when attempting to format prices into the non-given currency. When formatting a currency, the currency type should be checked. Likewise, the rules for adding/editing a package should be updated to require a currency to be set. |
Tyson Phillips (Inactive)
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Tyson Phillips (Inactive)
made changes -