View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002921 | MMW v4 | Other | public | 2007-03-15 16:51 | 2007-03-26 17:40 |
Reporter | rusty | Assigned To | |||
Priority | immediate | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 3.0 | ||||
Summary | 0002921: Debug Logs: Should be sent without user's email program | ||||
Description | On many occasions, the interface between Eurekalog and my email application doesn't work properly. e.g. -sometimes the log is generated to an email, but then the e-mail can't be sent (happens sometimes if MM has crashed) -sometimes the log isn't generated to an email, but it is in the clipboard so that it's possible to manually paste it -sometimes multiple emails are generated Finally, most users don't expect the current behaviour--the norm is that the application just sends the log. Isn't it possible to do this? | ||||
Tags | No tags attached. | ||||
Fixed in build | 1026 | ||||
|
I think that Petr has investigated this, but the problem was that this way we didn't get the user's e-mail address and so could reply and ask for more details. Question is: 1. Can't we send e-mail just using MM and just somehow try to get e-mail address from Outlook or other client? (Petr?) 2. Would it be that big problem if we don't get e-mail addresses of users? Probably yes, but maybe not that big if we force them to fill in some information about how to reproduce the problem... |
|
In the most recent builds, the Eurekalog dialog already prompts the user for: a) comments b) email address However, the text in the dialog is a bit vague so many users may not fill it in. Can we customize the text that appears in that dialog so that it's clear that we want them to provide this info so that we can reach them if we need help to solve the problem? More specifically, the current text is: ------------------------------------------------------------------------------ Please tell us about this problem. We have created an error report that you can send to us. We will treat this report as confidential and anonymous. To see what data the error report contains, _click here_. What were you doing when the problem happended (optional). ---------------------------------------------------- | ---------------------------------------------------- Email address (optional: ___________________________ [Send Error Report] [Don't Send] ------------------------------------------------------------------------------- To improve this we could change it to: ------------------------------------------------------------------------------- MediaMonkey.exe has encountered a problem......... ------------------------------------------------------------------------------- Please tell us about this problem. We have created an error report that you can send to us. To see the error report, _click here_. What were you doing when the problem occurred (optional)? ---------------------------------------------------- | ---------------------------------------------------- Can we contact you about this problem? If yes, please provide your Email address (optional): ___________________________ We will treat this report as confidential. [Send Error Report] [Don't Send] ------------------------------------------------------------------------------- |
|
Raised priority to 'immediate' since build 1023 doesn't allow an email address to be entered, and generates the following error when attempting to send an error log: [SMTP] Connection error: "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to repond" Socket log: |
|
Can you also make another tweak to the dialog: We have created an error report that you can send to us. --> We have created an error report that you can send to help us fix this. Also, the sentence 'To see what the error report...' should be immediately below the previous sentence (right now there's an extra blank line in between). |
|
fixed. For reporting bugs we're using HTTP. |
|
Tested in 1026 and it seemed to work. Need to test a bit further since there was a small bug that if the email field is > 17 characters, they don't appear (or they aren't typed at all). It seems to the user that the keystrokes aren't registered since the text in the dialog doesn't scroll left. |
|
Verified 1026. |