Bug 992629 - Uploading file with a semicolon in the filename causes filename to be truncated
Summary: Uploading file with a semicolon in the filename causes filename to be truncated
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Usability
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: David Mason
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On: 1066694
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-05 05:46 UTC by David Mason
Modified: 2015-07-31 01:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-31 01:22:23 UTC


Attachments (Terms of Use)

Description David Mason 2013-08-05 05:46:42 UTC
Description of problem:
If a filename contains a semicolon, only the component of the filename before the semicolon is used by Zanata, and a double-quote is prepended to to the filename.

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


How reproducible:
Always

Steps to Reproduce:
1. Create a file named test.txt;test.txt
2. Sign in as a maintainer of a project
3. Navigate to source documents page
4. Open upload dialog and select the file that has a semicolon in its name
5. Initiate the upload

Actual results:
File uploads successfully and is named (including double-quote character) "test.txt

Expected results:
File uploads successfully and is named test.txt;test.txt

Additional info:
This is caused by https://issues.jboss.org/browse/JBSEAM-4822

Comment 1 David Mason 2014-08-04 01:11:55 UTC
This problem will disappear when the seam file upload elements are replaced by the new multi-file upload widget. Once the new widget has proved stable in production, we can use it to replace all upload dialogs for which this problem occurs.

Comment 2 Zanata Migrator 2015-07-31 01:22:23 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-464


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