[ 
http://jira.magnolia.info/browse/MAGNOLIA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeff Snider updated MAGNOLIA-2045:
----------------------------------

    Attachment: mime-mapping-general-icon.diff

We ran into a similar issue with the download paragraph caused by this same 
thing.

We took a slightly different approach by removing the default value entirely 
from here and let the getMIMETypeIcon() function below handle the situation, 
since it was already written to do so.

Same outcome either way.  We've tested this in our dev systems and it takes 
care of both the dms and the download paragraph.

> Icon general.png not displayed in dms tree
> ------------------------------------------
>
>                 Key: MAGNOLIA-2045
>                 URL: http://jira.magnolia.info/browse/MAGNOLIA-2045
>             Project: Magnolia
>          Issue Type: Bug
>          Components: admininterface
>    Affects Versions: 3.5.4
>            Reporter: Capitaine Harold
>            Assignee: Philipp Bracher
>             Fix For: 3.5.5
>
>         Attachments: mime-mapping-general-icon.diff, MIMEMapping.patch
>
>
> Go in the dms section, add a new document as name.sh. The file icon is not 
> displayed because the image path is not good.
> The problem comes from the file MIMEMapping.java. When the load is done at 
> the beginning, if the mime mapping node doesn't contains an "icon" nodedata 
> it takes by default general.png instead of the constant DEFAULT_ICON that 
> contains the full path.
> See the patch in attachment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to