nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Doc icons based on Name property instead of Content Type...

theorbix

Hello,

I've noticed that in the 2.0x Web Client, the document type icons (showing Word, Excel, Acrobat, and other file formats) depend on the content of the Name property, instead of the Content type.

So, if I upload into an Alfresco repository a document, and I enter "My Presentation.ppt" in the Name property field, I'll see the PowerPoint icon, as expected.

But as soon as I rename the document name to "My Presentation", the document icon is changed to a generic document icon.

Is his "by design", or just small bug of the Web client?

In my opinion, the display of document/application icons shold be based on the value set in the Content Type drop down… this would allow users to use document names without the ".doc", ".xls", ".pdf" suffix…

Find more posts tagged with

Comments

gavinc

It is by design.

Feel free to raise this as a feature request in JIRA, you'll then be able to track it's progress.

theorbix

It is by design.

Feel free to raise this as a feature request in JIRA, you'll then be able to track it's progress.

Gavin,

Thanks for the prompt reply. I'll post an enhancement request.

What's the rationale for this design, by the way? I found it a bit awkward… so I was wondering what where the reasons "behind the feature"…

kevinr

The design choice was made very early in the web-client development. Basically at some points in the stack we only have the object name i.e. "something.txt" - and to work out what actual content object that was to find out the real mimetype (i.e. via a name path lookup of some kind) could be expensive performance wise. So the decision was made to use the file extension (which is always available) to lookup the icon filetype.

Thanks,

Kevin

martin_cowie

Kevin,

I've run into the same exact problem, thankfully this posting answered my prayers quickly enough. While creating my documents via the JCR interface, I have a mimetype value for each one of them. Is there a map( mime-type => suffix ) that I can draw upon to correctly suffix my documents at import? Clearly the webclient uses one …

Cheers,

M.

kevinr

Yes there is a public bean service called "MimetypeService" that provides mapping back and forward between extensions and known mimetypes.

Thanks,

Kevin