[MGNLNEWSLETTER-8] Invalid API keys and ListIDs should be reported in error/exception messages Created: 04/Jun/09 Updated: 16/Sep/15 Resolved: 30/Jul/09 |
|
| Status: | Closed |
| Project: | Newsletter (closed) |
| Component/s: | campaign-monitor |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Teresa Miyar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
When using a wrong listId or API key, the error message don't convey them, so it is difficult to see what's missing where. |
| Comments |
| Comment by Magnolia International [ 04/Jun/09 ] |
|
Done for API key - it is not so trivial for the list ID, since it can be passed to the methods of the interface - we don't necessarily use the configured one. |
| Comment by Michael Mühlebach [ 16/Sep/15 ] |
|
This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again. |