Details
-
Type:
New Feature
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.2.0-b1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Company settings should be added to allow a staff member to specify any number of custom CSS files and Javascript files to load into the structure.
We can cache the results so that performance is maximized.
Stylesheet: /app/view/client/default/css/ [ — name of CSS file here — ]
Javascript: /app/view/client/default/javascript/ [ — name of javascript file here — ]
Alternatively, (and perhaps a much better solution) we could allow the ability to specify the full URL to the file, which would allow users to pull javascript/css from some central repository (e.g. google code), etc.
------------------
Putting more thought into this. Perhaps it should just be a header input textarea nd a footer input textarea where custom HTML can be speicfied.
Activity
I concur with a header and footer text area.
Paul Phillips
added a comment - I concur with a header and footer text area. The data placed in the head or [bottom of the] body should be cached. If these settings are saved the cache should be cleared.
Additionally, this should update the preAction event to allow returning a couple variables:
- head
- body
Which will be included into the head or body tag of the rendered structure.pdt. This data will also be included in the cache.
Possible name for these cache files: structure_head, structure_body.
Cody Phillips (Inactive)
added a comment - The data placed in the head or [bottom of the] body should be cached. If these settings are saved the cache should be cleared.
Additionally, this should update the preAction event to allow returning a couple variables:
head
body
Which will be included into the head or body tag of the rendered structure.pdt. This data will also be included in the cache.
Possible name for these cache files: structure_head, structure_body. Give the addition of events that allow plugins to tie into the header/footer. Shouldn't this be a plugin instead?
Cody Phillips (Inactive)
added a comment - Give the addition of events that allow plugins to tie into the header/footer. Shouldn't this be a plugin instead? 
This should be included as options under the new settings section described in
CORE-961.