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
for instance, to set up a layer for water basins and another for mining concessions... Are those tiles from a tile server, or some GeometryCollection in local file in json...
Layer management in Leaflet
Thanks for responding. I was expecting that it be relatively easy to manage overlay layers (not the base layers that are indeed controlled form the Leaflet More Maps module's settings page)....
Layer management in Leaflet
We were able to add overlays and polygons to leaflet with a custom module as mentioned in https://github.com/backdrop-contrib/leaflet/issues/73#issuecomment-2907873081 with a combination of php...
Layer management in Leaflet