These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Bug Reporting error

First post
Author
Previous Topic Next Topic
Ferni Ka'Nviiou
Doomheim
#1 - 2015-02-08 10:12:55 UTC
I am composing a bug report, and I am trying to upload the images.

But the images keep failing to upload.
http://i.imgur.com/pyYGCtP.png

Why am I getting this error?
CCP Habakuk
C C P
C C P Alliance
#2 - 2015-02-09 21:24:49 UTC
Hmmm, could you try to upload a bit smaller images (try to save them as jpg)? While files with 2 - 3 MB should be working normally, I assume that the upload might be timing out with such large images.

CCP Habakuk | EVE Quality Assurance | Team Five 0 | (Team Gridlock)

Bug reporting | Mass Testing
Ferni Ka'Nviiou
Doomheim
#3 - 2015-02-10 04:53:40 UTC
Thanks Habakuk.

I had changed the file formats and size without success,
but I found the fix by using a different browser and re-writing the bug report.

The original images uploaded without problem after that.
CCP Habakuk
C C P
C C P Alliance
#4 - 2015-02-10 10:15:12 UTC
Ferni Ka'Nviiou wrote:
Thanks Habakuk.

I had changed the file formats and size without success,
but I found the fix by using a different browser and re-writing the bug report.

The original images uploaded without problem after that.


This is strange and very interesting to hear. Would you mind sharing with which browser it did not work?

CCP Habakuk | EVE Quality Assurance | Team Five 0 | (Team Gridlock)

Bug reporting | Mass Testing
Ferni Ka'Nviiou
Doomheim
#5 - 2015-02-10 10:29:30 UTC
CCP Habakuk wrote:
This is strange and very interesting to hear. Would you mind sharing with which browser it did not work?

Google Chrome - Version 40.0.2214.94 m

I restarted my computer, and I can now upload files with Chrome as well.
Prior to restart I had closed & relaunched the Chrome browser, and still received the same error.

So I suspect there was probably a temporary glitch either with Chrome or my computer, which had caused this.