View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004579 | Taler | taler-merchant-demos | public | 2016-06-11 19:00 | 2024-01-12 13:08 |
| Reporter | Christian Grothoff | Assigned To | Marcello Stanisci | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | 0.0 | ||||
| Target Version | 0.1 | Fixed in Version | 0.1 | ||
| Summary | 0004579: frontend needs admin interface to track transactions | ||||
| Description | Basically, the blog operator should have an "admin" interface where he can trace his sales/transactions. This interface should allow him to select a wire transfer identifier (copy & paste from his transaction history at the bank Web interface) and find out the various sales (transactions) that correspond to it (/trace/transfer returns a list of transaction IDs and amounts, and transaction IDs can then ideally be mapped by the frontend to the list of articles sold). Furthermore, the admin interface should have a transactions (articles sold), and it should be possible to look up the respective wire transfers (using the backend's /trace/transaction API). That way, we demonstrate how the site owner can check his business logic (i.e. map bank transfers to transactions and vice versa). | ||||
| Tags | No tags attached. | ||||
| Implementing the HTML part. Get this when forwarding the request to the backend { "error": "backend error", "response": "{\n \"error\": \"id argument missing\"\n}", "status": 400 } | |
| fixed in 76d2eab..719d053. Todo: translate JSON responses to HTML | |
| Get this: { "error": "backend error", "response": "{\n \"details\": {\n \"execution_time\": \"/Date(1473426571)/\"\n },\n \"exchange_status\": 202\n}", "status": 202 } UPDATE: it means that the exchange has not yet a wire transfer to show, so the frontend should not treat it as an error. | |
| handle 202 case. provide receiver-less way of submitting the form. | |
| Completed in f9e751b..94683dc. Other minor issues depend on merchant BE | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-06-11 19:00 | Christian Grothoff | New Issue | |
| 2016-06-11 19:00 | Christian Grothoff | Status | new => assigned |
| 2016-06-11 19:00 | Christian Grothoff | Assigned To | => Marcello Stanisci |
| 2016-09-08 15:55 | Marcello Stanisci | Note Added: 0011104 | |
| 2016-09-08 21:48 | Marcello Stanisci | Note Added: 0011105 | |
| 2016-09-09 13:32 | Marcello Stanisci | Note Added: 0011107 | |
| 2016-09-09 16:21 | Marcello Stanisci | Note Edited: 0011107 | |
| 2016-09-13 20:20 | Marcello Stanisci | Note Added: 0011115 | |
| 2016-09-14 13:32 | Marcello Stanisci | Note Added: 0011116 | |
| 2016-09-14 13:32 | Marcello Stanisci | Status | assigned => informing |
| 2016-09-14 13:32 | Marcello Stanisci | Resolution | open => fixed |
| 2016-09-18 22:51 | Christian Grothoff | Fixed in Version | => 0.1 |
| 2016-09-18 22:51 | Christian Grothoff | Target Version | 0.3 => 0.1 |
| 2016-10-11 15:28 | Christian Grothoff | Status | informing => closed |
| 2024-01-12 13:08 | Christian Grothoff | Category | merchant frontend (blog) => Merchant frontends (Python3) |
| 2026-08-23 14:16 | Florian Dold | Category | Merchant frontends (Python3) => taler-merchant-demos |