[MGNLDMS-96] sample DMS paragraph filters on 'extension' instead of 'type' Created: 01/May/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.1, 1.1.1
Fix Version/s: 1.x

Type: Bug Priority: Trivial
Reporter: Todd Farrell Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian/VMware, Magnolia CE 3.0.2 bundle


Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Please excuse me if this is not a bug; I may just not understand the DMS correctly

In modules/community/magnolia-module-dms/trunk/src/main/resources/mgnl-files/templates/dms/paragraphs/dms.jsp:

// search on file type
if(StringUtils.isNotEmpty(extension))

{ expressions.add("extension = '" + extension + "'"); }

I needed to change this to query based on the "type" attribute for it to work when specifying a particular extension (e.g. "pdf").



 Comments   
Comment by Magnolia International [ 14/Dec/07 ]

to be checked against latest release

Comment by Jan Haderka [ 05/Sep/08 ]

The confusion comes from the fact that DMS stores the file type separately in the String type node data called "type". Apart from that extension of the uploaded file is stored also as an "extension" attribute of the binary node data holding uploaded file data. So in theory you can use both to filter the query results. With the default dms configuration I was not able to create an situation in which value of "type" property and "extension" attribute would not be in sync. If you were able to create such situation, please describe it here.

Comment by Magnolia International [ 10/Sep/08 ]

will double check for 1.2.7 - as far as i can see, changing the extension of the file after the upload changes the type property in the document node, not sure about the binary subnode itself.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 00:48:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.