Bug 807197 - [Test Run]Error page when add attachment
Summary: [Test Run]Error page when add attachment
Keywords:
Status: VERIFIED
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.8.1
Assignee: Yang Ren
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-27 09:17 UTC by Jin Zhao
Modified: 2022-03-14 03:25 UTC (History)
5 users (show)

Fixed In Version: 3.8.0-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
Error page (74.64 KB, image/png)
2012-03-27 09:17 UTC, Jin Zhao
no flags Details
attachment (141.61 KB, image/png)
2012-03-27 09:18 UTC, Jin Zhao
no flags Details
The file's name is cut off before quotes. (142.67 KB, image/png)
2012-07-25 07:30 UTC, xubai
no flags Details
error2 (134.24 KB, image/png)
2012-07-25 07:31 UTC, xubai
no flags Details

Description Jin Zhao 2012-03-27 09:17:22 UTC
Created attachment 572997 [details]
Error page

Description of problem:
When I add attachment such as named "zh_CN_Document name_Redundant '​'.png" , After click upload button will show error page.
UnicodeEncodeError at /management/uploadfile/
'ascii' codec can't encode character u'\u200b' in position 81: ordinal not in range(128)

Version-Release number of selected component (if applicable):
3.6 on engineering 

How reproducible:
100%

Steps to Reproduce:
1.Enter to any test run, Ex https://tcms-stage.englab.bne.redhat.com/run/25224/
2.Expand any case run, click 'add' attachment
3.Browser file named "zh_CN_Document name_Redundant '​'.png"
4.Click 'upload'
  
Actual results:
Show error page as attachment

Expected results:
Can added

Additional info:

Comment 1 Jin Zhao 2012-03-27 09:18:33 UTC
Created attachment 572999 [details]
attachment

Comment 2 jianchen 2012-07-04 09:12:31 UTC
This bug was fixed in tcms 3.8.0.
Thanks.

Comment 3 xubai 2012-07-25 07:30:22 UTC
Created attachment 600232 [details]
The file's name is cut off before quotes.

Verify 3.8.0-1 on stage --> FAIL

Verify steps:
1.Enter to any test run, Ex https://tcms-stage.englab.bne.redhat.com/run/25224/
2.Expand any case run, click 'add' attachment
3 Browser file named "zh_CN_Document name_Redundant '​'.png"
4.Click 'upload'

Actual results:
The file's name is cut off before quotes. And when clicking the attachemnt, it shows error page as the attachment "error2".

Expected results:
Can added and view.

Comment 4 xubai 2012-07-25 07:31:52 UTC
Created attachment 600233 [details]
error2

Comment 5 Xiangyang Chu 2012-07-27 05:33:13 UTC
It was caused by server OS's environment setting,will support it in next build.
Thanks.

Comment 6 xubai 2012-07-31 06:52:17 UTC
(In reply to comment #5)
> It was caused by server OS's environment setting,will support it in next
> build.
> Thanks.

Verify 3.8.0-2 on stage --> FAIL

Description of problem:
The bug is still existed.

Verify steps:
1.Enter to any test run, Ex https://tcms-stage.englab.bne.redhat.com/run/25224/
2.Expand any case run, click 'add' attachment
3 Browser file named "zh_CN_Document name_Redundant '​'.png"
4.Click 'upload'

Actual results:
The file's name is cut off before quotes. And when clicking the attachemnt, it shows error page as the attachment "error2".

Expected results:
Can added and view.

Comment 7 yawei Li 2012-09-18 08:36:56 UTC
Temporarily provide warning info to user.
Will support special character in attachment name in TCMS 4.0. 
After release 3.8.1, will move this bug to 4.0

Comment 8 jianchen 2012-09-28 05:40:29 UTC
If upload a file with filename non-ascii, temporarily provide warning info.

Comment 9 Xin Gao 2012-10-10 07:57:55 UTC
Verify 3.8.1 on tcms-test -->PASS

Verify steps:
1.Enter to any test run, Ex https://tcms-stage.englab.bne.redhat.com/run/25224/
2.Expand any case run, click 'add' attachment
3 [details].Browser file named "zh_CN_Document name_Redundant '​'.png"
4.Click 'upload'

Actual result:
warning info were provided. "Upload File name is not legal."


Note You need to log in before you can comment on or make changes to this bug.