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
Hi Kevin I am interested assisting you developing a theme by cloning feature from existing WordPress website. Please let me know your suitable time to discuss further...
Create a theme from existing website
I've updated the Zulip link in both places I found it. No need to post again, unless you have something new to say. We'll pull together feedback from all the sources.
Backdrop CMS Core Priorities
Should we post here again, what we posted over there? Or would that unnecessarily duplicate things? The link to a Zulip thread in this initial post leads to an internal one, but there's...
Backdrop CMS Core Priorities