Document Library File Extension Handling creates isses with Sync
Description
Environment
Portal with Sync Client.
is related to
relates
Activity
Show:

Lawrence Lee February 14, 2012 at 11:16 PM
PASSED Manual Testing following the steps in the description.
Fixed on:
Tomcat 7.0 + MySQL 5. 6.1.x GIT ID: ffa69a16b821cceb9f925ffbe290840b63cca2fd.
Tomcat 7.0 + MySQL 5. 6.2.x GIT ID: c771e7e7873adb140b1c1fee9421acbba94b022b.
File system prompts user when changing extension. Liferay pulls filename+extension as the title.
Fixed
Details
Assignee
Lawrence LeeLawrence LeeReporter
Gail HernandezGail Hernandez(Deactivated)Labels
Branch Version/s
6.1.xBackported to Branch
CommittedFix Priority
5Git Pull Request
Components
Fix versions
Affects versions
Priority
Medium
Details
Details
Assignee

Reporter

Labels
Branch Version/s
6.1.x
Backported to Branch
Committed
Fix Priority
5
Git Pull Request
Components
Fix versions
Affects versions
Priority
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Zendesk Support

Linked Tickets
Created December 12, 2011 at 10:16 AM
Updated June 24, 2023 at 3:39 PM
Resolved March 12, 2012 at 2:25 PM
The few issue with with Sync, Document Library and File Extensions.
1) User adds file A.txt to portal.
2) User change name to A.
3) User starts sync and the file is downloaded. Since we use the title field to determine the file name we end up with file A with no extension which make opening the file problematic.
This isn't the only use case where this will be an issue. We discussed appending the extension onto the file when the file is download. However that will still cause problems if the user has file A and A.txt on the portal. There they are different files on the portal but would be the same to sync.
We'd like to move the portal to have the file name and title be the same thing. This way it keeps files unique and makes it easier to download files.
So the change would be when a file is uploaded, the title is the file name with the extension. When the user changes the title, the user is encouraged to keep an extension (like how the file system currently does). Users can choose not to have an extension, we don't force that.
We don't need to get rid of the extension column since it is used.
The change we're proposing is really only in the UI, so that it recommends that the user keep the extension that corresponds to the file's mime type, similar to what the mac does when you try to rename a file.
If we can do that, it will reduce the chance that the user will store a file without its extension and finally syncing to the file system without an extension.