When a file is attached to a node via a field, some handy features appear. A description field, for example, that allows users to hide the ugly file name and instead link some helpful description text.
Unfortunately, when building a view of all files, this helpful description text is lost, since it's not associated with the file, and instead is associated only with the node.
As we move file_entity into core I propose we move the file_description column from the field table to the file_managed table. Or, perhaps this could be our first default field on the file entity!
Either way, the end result should enable a user to build a view of PDFs that don't show the ugly file name but instead the pretty text that was provided for the link to the file, without needing to add a join to a field data table.
Recent comments
I do have the apache status page set up ... I will look in to this really fast. BRB.
Status Report Page throws : Forbidden You don't have permission to access this resource.
Hi TallElfin, that sounds like a webserver misconfiguration. It has nothing to do with the CMS itself. So... other paths work just fine, also admin paths, only the path "admin/...
Status Report Page throws : Forbidden You don't have permission to access this resource.
Hi Editing I see this: The CSS looks like this: /* Level 1: Standard Numbers */ .field-name-body ol { list-style-type: decimal; } /* Level 2: Lowercase Letters */ .field...
Numbered List format is different when editing