739 - Client reports "The request timed out" after successfully opening a ticket
What steps will reproduce the problem?
1. Submit a ticket using Curse Client v4's built-in issue reporting tool.
What is the expected output? What do you see instead?
I expected the client would either succeed at posting the ticket and report success, or fail and report failure. Instead, it succeeded at posting and then reported it had failed: I received a message that said "The request timed out," tried again and got the same message, then went to Curseforge to submit the ticket manually - only to discover that the client had successfully opened tickets 737 and 738 while reporting failure back to me.
What version of the product are you using?
4.0.0.297.
Do you have an error log of what happened?
Please provide any additional information below.
| User | When | Change |
|---|---|---|
| Kaelten | Thu, 22 Apr 2010 20:00:53 | Changed status from Accepted to Fixed |
| Kaelten | Thu, 04 Feb 2010 18:12:47 | Changed status from New to Accepted |
| mscottforbes | Thu, 04 Feb 2010 17:12:15 | Create |
- 1 comment
- 1 comment
Facts
- Last updated on
- 22 Apr 2010
- Reported on
- 04 Feb 2010
- Status
- Fixed - Developer made requested changes. QA should verify.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- Medium - Normal priority.
- Reply
- #1
Kaelten Thu, 04 Feb 2010 18:12:41I noticed that in your logs, I'll see what I can do.
WowAce.com & CurseForge.com Adminstrator
Check out my new addon, OneChoice, it helps you pick quest rewards faster.
Developer of Ace3, OneBag3, and many other addons and libraries
Project lead and Mac developer for the Curse Client