478249 - Testopia attachments unreadable after converting Bugzilla to use utf-8

Status: RESOLVED DUPLICATE of bug 473990

(Testopia :: General, defect)

Description

[dfishman]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729)
Build Identifier: Testopia 2.2 with Bugzilla 3.2

When using landfill testopia, I am able to attach MS Word document and then retreive it.

On my installation, MS Word gets confused with encoding and text shows as question marks.  This was working when I had Bugzilla 3.0.5 with earlier Testopia version.  While upgrading to Bugzilla 3.2, I converted to using utf-8. I suspect that Testopia was not properly converted to using utf-8

Reproducible: Always

Steps to Reproduce:
1. Attach simple English word document to Testopia test plan
2. Attach the same document to Bugzilla bug
3. Retreive Bugzilla attachment of step 2
4. Retreive Testopia attachment of step 1
Actual Results:  
Bugzilla attachment opens and is readable
Testopia attachment opens and is not readable.  MS Word offers a menu of encodings to try, but none works.


When using landfill testopia, I am able to attach MS Word document and then retrieve it.

On my installation, this was working when I had Bugzilla 3.0.5 with earlier Testopia version.  

While upgrading to Bugzilla 3.2, I converted to using utf-8. 
Then I upgrade to Testopia 2.2 I suspect that Testopia was not properly converted to using utf-8.

Comment 1

[dfishman]

Attachment: simple English word document to use as a test attachment

Comment 2

[dfishman]

Attachment: Snapshot of MS Word attempt to view Testopia attachment

Comment 3

[dfishman]

Blob data in test_attachment_data table and attach_data are identical, so the error must be happening during retrieval of testopia attachment

Comment 4

[Greg Hendricks]

It sounds like this may be a duplicate of bug 473990. But this was fixed prior to final 2.2 release. Are you running the beta?

Comment 5

[dfishman]

Correct. Upgraded from Bet to 2.2 and problem is fixed.