-
☆ A M B ☆
- 24,524 Posts
In the main menu item "Content" there is a sub-menu item "Import Static Resources". I would presume that this is to be used to generate Static Resources from directories full of files. But the text and the form fields don't all make sense.
What is this supposed to do?
For example,
Using this tool you can import resources from a set of static files into the database. Please note that you will need to copy your files and/or folders into the core/import folder.
How would this be of any use if your files are going to be stored in assets/files/docs/? This seems to be in conflict with the first field, for entering the base file path. Or will you need to copy all of your files into core/import/, as well as specify the actual base path where you will be actually storing the files and linking to? Sort of like a media source in reverse?
The root HTML element to import also doesn't make sense in this context. The content of a Static Resource is just the path to the file.
This looks like it is intended to be a hybrid import, incorporating the HTML import feature as well as Static Resource generation.
I wonder if the heading should be something like, "Create Resources from HTML Files." I suspect that it produces regular resources rather than static resources and that it means "static" in the sense of "not in the DB."
-
☆ A M B ☆
- 24,524 Posts
There already is the usual "Import HTML" menu option. The description text for the both of them are almost identical, but it looks to me like it's intended to morph into a "generate any type of resource" replacement for the Import HTML feature. It does have a field to indicate which type of resource to import into, so if it's going to be creating Static Resources, one of two things have to happen.
Either it can import from any given path, or if it does have to import from the core/import directory, then Static Resources would have to be able to use Media Sources in order to be properly linked to the actual files in their actual location. Ideally, Static Resources need to work with Media Sources so that they can be linked to files outside of the web root, as well as to files in external storage systems like Amazon S3 or BitBucket or even a corporate file repository. Then Static Resources would really fly.
I stand corrected.
In that case, I don't know what the deal is with them. Time for some trial and error I guess.
