Dating internet directorise Free sexy webcam sites
It doesn't seem a likely scenario but its possible someone could do it.
We already have a way to make this happen - there is a setting in the file field configuration, but it's default is nothing, which means all files get dumped into the public directory.
)You would be surprised about the amount of sites that are not "enterprise" but have this many files.
Let's discuss *how* to make this happen and choose a pattern later.
Additionally, as attiks said, certain situations (such as content migration) may result in the creation of too many files on a given day.
I agree that we should have a dynamic default, but it should not be date-based.
Let's change default location configuration variable in file/image fields.
Discussing how to make this happen means choosing a pattern [email protected]: Always consider that adding files to new content means we don't have context such as ID.
Also, we'd need to fix that the token replacement when the file uploaded has no context related to it's parent entity at all (see file_field_widget_uri() and nothing that calls this function uses the $data [email protected]: Sure, it would require some major changes to file fields, but it might be worth a try in order to get that context.
The amount of files caused severe problems for the underlying filesystem, leading to data corruption.
We should have safe defaults, so I propose providing a mechanism in core to prevent this kind of data corruption.
Users can affect this by changing configuration of file/image fields, but real-world experience shows that they don't.