Document library portlet accepts different file extensions for document versioning

• Type: Regression Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 6.0.5 GA
• Fix Version/s: --Sprint - SP, 6.1.0 CE RC1
• Component/s: DM > Document Library Display
• Labels: None
• Environment: Tomcat+ mysql revision 59500, firefox
• Similar Issues: Show 5 results ; ;

  LPS-10770	When editing a file in Document Library the extension of the new file must match the extension of the previous versions
  LPS-10979	When downloading a previous version of a document library file the name of the downloaded file is different
  LPS-14856	Uploading a file with valid extension and different name without an extension should be valid
  LPS-19951	Document Library FileEntry extension not changing if a new version of the file has a different extension
  LPS-10980	Editing the name of a file in Document Library doesn't update the extension

Add Document Library > Add Document with *.txt extension.

edit the document and load a document with *jpg extension.

It should not allow you to load a jpg as a version for a txt document.

[Jorge Ferrer]

This is not a bug. There is a property that allows or disallows this behavior:

#

1. Set this to false to allow users to update file entries by uploading a
2. file with an extension different from the one of the originally uploaded
3. file. There is a known issue where setting this to true will break OSX
4. compatibility. See LPS-10770 for more information.
   #
   dl.file.extensions.strict.check=false