View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 3044 | Composr | ecommerce | public | 2017-01-25 13:14 | 2017-02-14 17:47 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 3044: More robust flow through payment gateways | ||||
| Description | Currently we pass either an item name & product ID through a payment gateway, or a trans expecting ID which then let's us find the item name & product ID from the ecom_trans_expecting table. We should consistently move to the latter, with sometimes an item name going through as a *label* only. This has 4 advantages: 1) We can replace the 'search' method for finding products within hooks using item names to a simpler handles_product method. This is more efficient and easier to understand. 2) If the price changes mid-purchase we can rely on the ecom_trans_expecting record to have locked in the original price, avoiding an error. 3) Consistent. All hooks would do it in one way. 4) We don't have to worry about item names being unique, only the product codenames would need to be. A ecom_trans_expecting record would only be valid for a configured length of time, default to 2 weeks. Beyond that an error message would show. | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Time estimation (hours) | 5 | ||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-01-25 13:14 | Chris Graham | New Issue | |
| 2017-02-14 17:47 | Chris Graham | Status | Not Assigned => Resolved |
| 2017-02-14 17:47 | Chris Graham | Resolution | open => fixed |
| 2017-02-14 17:47 | Chris Graham | Assigned To | => Chris Graham |
