Requirements
class Requirements implements Flushable (View source)
Requirements tracker for JavaScript and CSS.
Properties
static private bool | $disable_flush_combined | Flag whether combined files should be deleted on flush. |
Methods
Triggered early in the request when a flush is requested
Enable combining of css/javascript files.
Checks whether combining of css/javascript files is enabled.
Set the relative folder e.g. 'assets' for where to store combined files
Set whether to add caching query params to the requests for file-based requirements.
Check whether we want to suffix requirements
No description
Register the given JavaScript file as required.
Register the given JavaScript code into the list of requirements
Return all registered custom scripts
Register the given CSS styles into the list of requirements
Add the following custom HTML code to the
section of the pageInclude the content of the given JavaScript file in the list of requirements. Dollar-sign variables will be interpolated with values from $vars similar to a .ss template.
Register the given stylesheet into the list of requirements.
Registers the given themeable stylesheet as required.
Registers the given themeable javascript as required.
Clear either a single or all requirements
Restore requirements cleared by call to Requirements::clear
Block inclusion of a specific file
Remove an item from the block list
Removes all items from the block list
Update the given HTML content with the appropriate include tags for the registered requirements. Needs to receive a valid HTML/XHTML template in the $content parameter, including a head and body tag.
Attach requirements inclusion to X-Include-JS and X-Include-CSS headers on the given HTTP Response
Add i18n files from the given javascript directory. SilverStripe expects that the given directory will contain a number of JavaScript files named by language: en_US.js, de_DE.js, etc.
Concatenate several css or javascript files into a single dynamically generated file. This increases performance by fewer HTTP requests.
Return all combined files; keys are the combined file names, values are lists of files being combined.
Delete all dynamically generated combined files from the filesystem
Deletes all generated combined files in the configured combined files directory, but doesn't delete the directory itself
Re-sets the combined files definition. See {@link Requirements_Backend::clear_combined_files()}
Do the heavy lifting involved in combining (and, in the case of JavaScript minifying) the combined files.
Set whether you want to write the JS to the body of the page rather than at the end of the head tag.
Set whether to force the JavaScript to end of the body. Useful if you use inline script tags that don't rely on scripts included via {@link Requirements::javascript()).
Output debugging information
Details
static
flush()
Triggered early in the request when a flush is requested
static
set_combined_files_enabled(bool $enable)
Enable combining of css/javascript files.
static bool
get_combined_files_enabled()
Checks whether combining of css/javascript files is enabled.
static
set_combined_files_folder(string $folder)
Set the relative folder e.g. 'assets' for where to store combined files
static
set_suffix_requirements($var)
Set whether to add caching query params to the requests for file-based requirements.
Eg: themes/myTheme/js/main.js?m=123456789. The parameter is a timestamp generated by filemtime. This has the benefit of allowing the browser to cache the URL infinitely, while automatically busting this cache every time the file is changed.
static bool
get_suffix_requirements()
Check whether we want to suffix requirements
static
backend()
static
set_backend(Requirements_Backend $backend)
Setter method for changing the Requirements backend
static
javascript(string $file)
Register the given JavaScript file as required.
static
customScript(string $script, string|int $uniquenessID = null)
Register the given JavaScript code into the list of requirements