Bug fix where static files are removing if automated static files are turned off

[sdrenth]

This fixes the issue where old static files where removed even if the automate static files system setting was turned off for that element type.

What does it do?

I've added a system setting check that checks if static files are automated for the current element type.

Related issue(s)/PR(s)

Issue: #14206
PR that created the issue: #14135

[JoshuaLuckers]

What happens if you select the wrong file by accident (like index.php), save it and change it to the correct file afterwards?

Is it possible to have those files move to a "trash folder" instead of deleting them from the filesystem immediately?

[sdrenth]

@JoshuaLuckers I don't think a trash folder is necessary. If you set up your static file structure correctly the source does not have access to files such as index.php

[alroniks]

What is type is an empty string? In this case, all times will be called wrong setting. Make sense fetch setting value only when the type is defined.

[tolanych]

I tested this PR (reproduced from #14206 (comment)) for setting static_elements_automate_chunks.

When this settings as Yes - previous static file removed from file system.
When this setting as No - previous static file stay.

[JoshuaLuckers]

I tested the following with static_elements_automate_* turned off:

• If I change the static file for an element the old file is not deleted (good).
• If I delete an element that uses a static file the static file is deleted (not good).

[Jako]

@JoshuaLuckers Your issue should be fixed with #14228. But this PR covers another part.