MODX Staff
<?php
// &file=`assets/foo/bar.php` indicates the file to include
// &return=`1` return explicit content from return statement in included file
// default behavior is to use output buffering to capture the content from the include
$output = '';
if (isset($file) && file_exists($file)) {
if (!isset($return) || $return == false) {
ob_start();
include ($modx->config['base_path'] . $file);
$output = ob_get_contents();
ob_end_clean();
} else {
$output = include ($modx->config['base_path'] . $file);
}
}
return $output;
?>
MODX Staff
If you are willing to treat chunks and templates as simple includes from a snippet, you could use this for that as well, but yes, this is the code for a snippet that includes an external file. You can theoretically build your whole site with one snippet in the manager this way, but this may circumvent certain [existing 3rd party] components that expect things to be stored in the DB, or certain parts of the caching mechanisms.
Thanks for the reply. I understand what that code does and this may be a dumb question, but where exactly does that code go? As far as I understand, PHP can only be run inside of snippets. What do I do for chunks and templates?
Or is that the code for a snippet that includes an external file?